3 ms·
microsoft wasted its time rewriting dotnet to catchup with java nobody moved, instead they had other needs, GO appeared, and people adopted it what's left? pe
by Shadonototra 5y ago
microsoft wasted its time rewriting dotnet to catchup with java
nobody moved, instead they had other needs, GO appeared, and people adopted it
what's left? people maintaining Java servers; and when it's time to switch tech, it's GO
politics is what ruined C#, now they are bloating the language with features nobody asked/needed
microsoft have the wrong culture, they are bloat oriented, and they are vendor locking driven
it's either ASP.NET or nothing with C#, that says it all
and you still CAN'T build a AOT statically compiled single file executable, you have to ship your 300 DLLs with you, even that, they couldn't improve, it's 2021, it's a billion dollar company, and yet, it's still "we are working on it", dude no, it's too late, i'll go with GO
for a while they recommended zipping/unzipping at runtime your 300+dll folder as a solution to the "single file problem", so no, you can't come up and say, "we are awesome piece of tech", because that's a pure lie, a billion dollar company
and msbuild, while it has improved, it still a joke compared to what other languages are providing, not worse than gradle or maven, but equally shitty
https://news.ycombinator.com/item?id=28655192 https://news.ycombinator.com/item?id=28655192 200mb + 300 DLLS for a desktop application, that's the "awesome" dotnet for you, even java don't do that anymore
- simooooo 5y agoSo you’re saying you like go?
- merb 5y ago> https://news.ycombinator.com/item?id=28655192 https://news.ycombinator.com/item?id=28655192 200mb + 300 DLLS for a desktop application, that's the "awesome" dotnet for you, even java don't do that anymore btw. thats paint.net which comes WITH the runtime. it's not just a "small" desktop application. now deploy a java desktop application WITH the runtime and look how "big" it is.
- pjmlp 5y agoJava 9 dropped the runtime, whoever keeps doing it Java 8 style cannot get past old habits. The correct way is to use the java linker and distribute jvm.{so, dll} alongside a trimmed runtime.
- HideousKojima 5y ago>and you still CAN'T build a AOT statically compiled single file executable, you have to ship your 300 DLLs with you, even that, they couldn't improve, it's 2021, it's a billion dollar company, and yet, it's still "we are working on it", dude no, it's too late, i'll go with GO I published a single file executable just last week, what in the world are you talking about? If there are any native code DLLs you have to include 1 extra line in your .csproj file to get those to be included in the single file, but other than that it works without any issues whatsoever. Literally spits out a .exe and a .pdb file and nothing else.
- pjmlp 5y agoWhich kind of AOT flavour? NGEN, .NET Native, the pseudo extract zip, the pseudo extract zip with mmap execution,..... https://github.com/dotnet/designs/blob/main/accepted/2020/form-factors.md#native-aot-form-factors https://github.com/dotnet/designs/blob/main/accepted/2020/fo... Even in .NET 6 it is going to be "almost there, wait a bit more for .NET 7 to cover all use cases". https://devblogs.microsoft.com/dotnet/announcing-net-6-preview-6/#comment-9721 https://devblogs.microsoft.com/dotnet/announcing-net-6-previ...
- HideousKojima 5y agoI was referring to the previous commenter's claim about publishing single file executables, not AOT compilation. AFAIK, true AOT compilation is still only possible with Mono, not .NET Core. Though the line between those is getting blurrier all the time now, since I'm pretty sure Mono is what is technically used if you publish a Xamarin app for iOS, even if you technically developed it in .NET Core/6.
- pjmlp 5y agoFair enough, although that is the whole problem with the .NET team and AOT. If I recall correctly they did at least three surveys asking us what did we mean by AOT compilation. Apparently they use another dictionary at Redmond, duh.