4 ms·
Well, in my opinion they actually do need to have strong opinions because it's not "just another node framework". They want to target enterprise sooner than lat
by romanovcode 10y ago
Well, in my opinion they actually do need to have strong opinions because it's not "just another node framework". They want to target enterprise sooner than later and it doesn't hurt that you have huge megacorp backing the product, of course it also makes their saying much more weightful.
Also, I don't see the problem with the changes, they announced that they are going away from JSON to XML like 3 months ago and it's not like this is news.
Also, I like XML much better for project files because IMO it's much more readable.
- vmarsy 10y agoI like the XML format better too. It's also easier* to parse if you start using XPath, if for any reasons you need to quickly read/write some of the values. * Except when a default namespace is involved, then XPath expressions get more complicated. But according to that blog, it looks like the VS team ditched the default xmlns="http://schemas.microsoft.com/developer/msbuild/2003" http://schemas.microsoft.com/developer/msbuild/2003" namespace in the <Project> root :)