Hacker News Reader

Comment by konsuko | Hacker News Reader

I can definitely say that for me, this is the straw that breaks the camel's back. I am turning my back on the .NET ecosystem, after having written C# for 7 years. The `dotnet watch` debacle from last year, still having key parts like the debugger closed-source and now again with this: It's just too much.

I do not want to build anything of value on top of such a shady platform that's completely controlled by one Megacorporation. It's too big of a risk.

No matter how many MVPs tout "MS <3 Open Source", how can anyone still believe them after these repeated violations?

View on HN

.NET was open sourced in 2016, that's 6 years ago. It looks like you were 1+ years fully within the ecosystem before any part of it was OSS, and now you're demanding new features they write get open sourced as well?

Reminds of that time they introduced WiFi on planes; it was a brand new thing, and they let folks on the flight use it for free - but of course being a new tech it broke down after about an hour. There was this guy on the flight making a big fuss about the WiFi stopping working, like truly upset and vocal about it. Dude, how are you owed something you didn't even know existed an hour ago?

They replace an existing open source feature with a closed source one.

So that's totally different.

No they don't, they give you a choice between the existing open source solution and a new closed source one.

I agree with this sentiment, but you forgot to credit Louis CK for the anecdote you borrowed.

He should steal material from less well-known comedians. That's what the pros do.

Ah, a connoisseur! :)

The problem with MVPs is that they are effectively Microsoft sponsored marketing outlets. I know a few of them personally and they are great people but damn have they drunk the kool-aid.

To a degree where they are pointless as a consumer but also pointless as an input gatherer.

MVP are pointless.

It's not only that debugger is closed-source - if you try to run non-MS provided build of VS Code, the .Net debugger would decline to start. That was very surprising, after installing VS Code on ubuntu from some default package.

is `dotnet watch` basically `git ls-files|entr dotnet build` ?

(entr is http://eradman.com/entrproject/ – like inotifywait but easier)

It may as well be. It can do some legit hot reload, but the set of scenarios where it works is so small it’s effectively useless.

Yea, the drama occurred when it was in preview, so we all thought it's going to have real hot-reload capability as we know from webdev.

I think it also replaces the running code on the fly.

No, it has a lot of bytecode level intelligence to surgically replace the parts of the program that need replaced (as I understand it). Your version just re-runs the project from scratch whenever a change occurs.

Reply on news.ycombinator.com