Outdated. Microsoft has clearly embraced open source, and is facilitating cross-platform .NET development (OmniSharp, ASP.NET 5). Async is a thing. SQL Server is not a con, switch to something else. Mono is reason to leave mono, not .NET.
Why I Left the .NET Framework (2013)
31–40 of 113 posts
Re: Why I Left the .NET Framework (2013)
#32Earlier quoted context omitted.
What are advantages of Python over C#?
> What are advantages of Python over C#? Well, a major one that comes to mind (and may change as things progress) is application portability. The open CLR project hasn't gotten far enough yet to truly be cross-platform capable. It's also smaller in weight and baggage, some argue faster to prototype/develop-in, community driven (no decade of a single company's inner departments fighting over features and behaviors), i…
The major one you list is an advantage of the runtime, not the language. I don't see how NIH matters -- if C# is good, why does it matter that Microsoft built it because they couldn't control Java?
Re: Why I Left the .NET Framework (2013)
#33Some of this criticism was outdated already, or has gone out of date since. WebForms (with their underlying concept of abstracting away how web really works) were already in decline two years ago, replaced by MVC. As a former C# developer, turned Android developer, of course I have to admit there is some walled garden mentality among .NET devs, but I think they get stigmatized for that way more than average. If a Rub…
> they get stigmatized for that way more than average. If a Rubyist never sticks nose outside their beloved technology stack, noone makes such a big deal out of it. Yes, exactly right. > to vitriolic anti-M$ hater mentality Right on - this isn't what OP was demonstrating, I think, but general reactions to Microsoft technologies are pretty bizarre. Use it or don't, but I don't get all the hate.
To be clear, I certainly wouldn't put OP in hater category, I disagree with some of his statements but his article is balanced and substantive. Unfortunately this is not the standard
Re: Why I Left the .NET Framework (2013)
#34Some of this criticism was outdated already, or has gone out of date since. WebForms (with their underlying concept of abstracting away how web really works) were already in decline two years ago, replaced by MVC. As a former C# developer, turned Android developer, of course I have to admit there is some walled garden mentality among .NET devs, but I think they get stigmatized for that way more than average. If a Rub…
> often directed at developers themselves
Who else should it be directed at ? the janitor ? If you have a problem with something, direct it toward its creator.
Re: Why I Left the .NET Framework (2013)
#35From 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…
Amusingly, in his "Why I love Go" [0] linked from that article he discusses using the right tool for the job:
> Instead, this about the right tool for the job. (Could you imagine woodworkers getting into heated arguments about whether a screwdriver or hammer was better?)
That would be about as insane as a woodworker writing a blog post about 'leaving the screwdriver' :)
Re: Why I Left the .NET Framework (2013)
#36Some of this criticism was outdated already, or has gone out of date since. WebForms (with their underlying concept of abstracting away how web really works) were already in decline two years ago, replaced by MVC. As a former C# developer, turned Android developer, of course I have to admit there is some walled garden mentality among .NET devs, but I think they get stigmatized for that way more than average. If a Rub…
> they get stigmatized for that way more than average. If a Rubyist never sticks nose outside their beloved technology stack, noone makes such a big deal out of it. Yes, exactly right. > to vitriolic anti-M$ hater mentality Right on - this isn't what OP was demonstrating, I think, but general reactions to Microsoft technologies are pretty bizarre. Use it or don't, but I don't get all the hate.
The hate comes from the iron-fist mentality MS has and had toward its users, and their lack of reliability and lack of responsibility for their part in delivering an unreliable product. Why don't you "get" that ?
Re: Why I Left the .NET Framework (2013)
#37I've been on two interviews recently, and both saw experience in .NET as a negative. I found myself having to down-play experience in .NET in both cases, in order to guide the discussion toward more applicable skills for the role. Even when you may be a polyglot programmer, interviewers tend to label you as .NET or Microsoft. Which, has apparently become a bad thing. Unless you're interviewing with a Fortune-100 comp…
It would probably be pretty crappy to work under technical leadership with that kind of mind set anyway.
Re: Why I Left the .NET Framework (2013)
#38I've been on two interviews recently, and both saw experience in .NET as a negative. I found myself having to down-play experience in .NET in both cases, in order to guide the discussion toward more applicable skills for the role. Even when you may be a polyglot programmer, interviewers tend to label you as .NET or Microsoft. Which, has apparently become a bad thing. Unless you're interviewing with a Fortune-100 comp…
I would think twice about joining an organization that thinks negatively of your former experience in a different stack. Sure, they may not be relevant to the job at hand, but good programmers will write good code in whatever stack they have to work in.
Re: Why I Left the .NET Framework (2013)
#39Interesting that he didn't mention the core idea of this piece that got a fair amount of attention: http://www.aaronstannard.com/the-profound-weakness-of-the-ne... Namely, hat .NET developers don't really solve any hard problems
Ironically I think there a lot of distributed platforms for .net.
NServiceBus, MassTransit. Akka.net, Orleans, etc
Re: Why I Left the .NET Framework (2013)
#40Some of this criticism was outdated already, or has gone out of date since. WebForms (with their underlying concept of abstracting away how web really works) were already in decline two years ago, replaced by MVC. As a former C# developer, turned Android developer, of course I have to admit there is some walled garden mentality among .NET devs, but I think they get stigmatized for that way more than average. If a Rub…
> often directed at developers themselves Who else should it be directed at ? the janitor ? If you have a problem with something, direct it toward its creator.
I mean people who code in .NET to make a living, contrary to the stereotype purported by haters most of them are not brainwashed Microsoft fanboys