Why I Left the .NET Framework (2013)
blog.jonathanoliver.com
Why I Left the .NET Framework (2013)
1–10 of 113 posts
Re: Why I Left the .NET Framework (2013)
#2[deleted]
Re: Why I Left the .NET Framework (2013)
#3tl;dr version - it's mostly about the portability, shortcomings of Windows as OS, and accompanying software (VS, TFS, IIS, MSSQL etc) being bloated. Zero critics about the .NET framework itself.
Re: Why I Left the .NET Framework (2013)
#4From the comments: "Why do people have to "leave" technologies? Why can't they just add new technologies to their arsenals without dramatic quitting blog posts? You don't see musicians who have just learned to play the guitar writing "why I'm leaving the piano" posts. Go is great; Node.js is great; some JVM languages are fine; .NET has a hell of a lot going for it too. Evaluate your options at the start of every project and use the best tool for the job at hand."
Re: Why I Left the .NET Framework (2013)
#5tl;dr version - it's mostly about the portability, shortcomings of Windows as OS, and accompanying software (VS, TFS, IIS, MSSQL etc) being bloated. Zero critics about the .NET framework itself.
I think that does a great disservice to the article by not acknowledging the commentary about the availability of quality OSS and the poor quality of the community/culture
Re: Why I Left the .NET Framework (2013)
#6Author states "Using the Disruptor (a lock-free ring buffer on the JVM), you can easily process 20M+ events per second. On .NET using ordained "best practices" anything more than a dozen transactions per second is considered decent-to-good performance and at that point, you just need bigger/better/more hardware."
WTF? This is inane.
Re: Why I Left the .NET Framework (2013)
#7From the comments: "Why do people have to "leave" technologies? Why can't they just add new technologies to their arsenals without dramatic quitting blog posts? You don't see musicians who have just learned to play the guitar writing "why I'm leaving the piano" posts. Go is great; Node.js is great; some JVM languages are fine; .NET has a hell of a lot going for it too. Evaluate your options at the start of every proj…
Did anyone else feel happy wave of nostalgia when reading this title? I haven't seen a "Why I'm leaving X" post for many years!
Re: Why I Left the .NET Framework (2013)
#8From the comments: "Why do people have to "leave" technologies? Why can't they just add new technologies to their arsenals without dramatic quitting blog posts? You don't see musicians who have just learned to play the guitar writing "why I'm leaving the piano" posts. Go is great; Node.js is great; some JVM languages are fine; .NET has a hell of a lot going for it too. Evaluate your options at the start of every proj…
That's the more successful way of thinking, if you ask me.
Re: Why I Left the .NET Framework (2013)
#9tl;dr version - it's mostly about the portability, shortcomings of Windows as OS, and accompanying software (VS, TFS, IIS, MSSQL etc) being bloated. Zero critics about the .NET framework itself.
I think that does a great disservice to the article by not acknowledging the commentary about the availability of quality OSS and the poor quality of the community/culture
Meh, not a great disservice.
Re: Why I Left the .NET Framework (2013)
#10> C# is awesome. I think it's a spectacular language.
OCaml, Haskell and Lisp are spectacular. Erlang is spectacular. Tcl and Python are spectacular. C# is an OK-language at best.
> I'm not aware of any non-Java JVM languages prior to the CLR [...]
Except JVM/Java had JPython, JRuby, and Rhino (JavaScript) earlier. Those are interpreted, sure, but they were running inside JVM and talking to Java code already when .NET was first published. The compilation to JVM bytecode is a minor implementation detail.