Nmake vs msbuild

Nmake and msbuild are both command line automatic compilation systems with similar functions. Now VS 2005 has adopted the msbuild system.
The nmake format is straightforward and the file is simple:
Proxy. OBJ: .. \ proxy. C .. \ putty. h .. \ Network. h .. \ proxy. h .. \ puttyps. h \
.. \ Misc. h .. \ windows \ winstuff. h .. \ Mac \ macstuff. h \
.. \ MacOSX \ OSX. h .. \ UNIX \ Unix. h .. \ puttymem. h .. \ tree234.h \
.. \ Windows \ winhelp. h .. \ charset. h
CL $ (compat) $ (cflags) $ (xflags)/C .. \ proxy. c

Msbuild uses XML files:
<Compile include = "form1.cs">
<Subtype> form </subtype>
</Compile>
<Compile include = "form1.designer. cs">
<Dependentupon> form1.cs </dependentupon>
</Compile>

Compared with the two, msbuild is a rising star, but it feels that it is more difficult to manually edit the file than the former. If it is purely an IDE, it is of course no problem to maintain the file, but it makes trouble for developers who need manual configuration. Read/Enter lengthy XML tags. Msbuild may bring a lot of innovation, but I have to regret that he is more away from humans.
Some people complained on the Internet:

Http://blog.manno.org/2006/05/18/why-msbuild/