Hacker News Reader

Comment by benaadams | Hacker News Reader

The changes have been announced well ahead of being designed or implemented; so at this stage are "proposed" changes.

There are issues on github where they are working through various designs; people are giving feedback, they are listening to them, iterating, improving - they written blogs about why, again taking feedback responding etc

So that's pretty early community on-boarding - its not like they have already designed and implemented it without consultation and did a surprise change - its still in an open design phase.

View on HN

The changes were announced ahead of time, but within the discussion there hasn't really been actual consideration around not switching back to MSBuild. They've been pretty set on the it within the Github issues (#1433) and haven't provided too much reasoning for it outside of tooling. Of course it's not that alone either there is just a bunch of confusion around it right now on the direction of .NET Core.

From one of the end comments:

> If you want to work out how it should be made and be in the design team that talks about it... please do. [Link to MS Career Page]

There were two blog posts around the why:

Making it easier to port to .NET Core https://blogs.msdn.microsoft.com/dotnet/2016/05/27/making-it...

Changes to Project.json https://blogs.msdn.microsoft.com/dotnet/2016/05/23/changes-t...

Scott Hunter, Damain Edwards and Jon Galloway recently did a live community standup video about them https://youtu.be/YJsQ3tnS7Ew?t=10m39s

I get that they have gave their reasoning (all those links were already grayed out), but its much more an announcement than it is a discussion. In the end though, it feels more like an executive decision than a collective push.

Yeah, they actually hold meetings with the community on Google Hangouts where they literally discuss every move in the open. Just because you aren't following it doesn't mean that it isn't happening.

Entirely aware they do, even watched the relevant part for the csroj piece today; however, not everyone has time to sit through the stand-ups. And when the discussion with the community blows up on Github things don't look as promising as they once did. Sorry I don't share your same sentiment, but I am seemingly not alone in how I feel.

If it really bothers you and you don't believe your concerns will be taken into account and there is a huge ground swelling of community support, its Apache 2.0 Licensed, fork it and make something better that fits with your vision: https://github.com/dotnet/roslyn-project-system

Its OSS, nothing stopping you...

Damn I like to complain not code, that's why I'm on HN right now.

Reply on news.ycombinator.com