> Why I Moved Away From Microsoft ASP.NET Because its almost 2014?
That's the common reason people* move to/away from various technologies.
* under 25
Why I Moved Away From Microsoft ASP.NET
11–20 of 110 posts
Re: Why I Moved Away From Microsoft ASP.NET
#12I miss C# something rotten. It's such a great language, and I miss being able to use stuff like LINQ every day. But the community just isn't here - everyone is working on huge-scale corporate projects, and comparatively few are working on great stuff like Nancy.fx (a lightweight web MVC framework). That said, I bought a license for MonoTouch, and I'm hoping that I'll be able to use C# for cool stuff in the future. Ju…
this is the same thing in almost any community. You have a handful of people who are dedicated to the open source movement of the language and the reset just sit by the sidelines. There's nothing wrong with this though. Not everyone has spare time in their lives to dedicate to open source.
I think it's different when the language has open source roots. A ton of ASP.NET libraries are paid products, and support for them comes at a premium. You don't see that anywhere near as much in Ruby or Node.
Re: Why I Moved Away From Microsoft ASP.NET
#13One of the first tasks the new CEO will have when Ballmer leaves is the job of convincing Enterprise customers that Microsoft is still here to fill their needs. That said, the conclusions the author came to may very well be true for classic "Web Forms" projects, and though he noted MVC... i don't feel like he gave it the proper time it deserves. In fact, I find almost the opposite of his sentiments to be true. MVC is…
One of the first tasks the new CEO will have when Ballmer leaves is the job of convincing Enterprise customers that Microsoft is still here to fill their needs
I don't think that Enterprise customers are the problem- they already use MS all the time. It's the small to medium size companies that aren't using it - and as they become larger companies it will become a problem for MS.
Re: Why I Moved Away From Microsoft ASP.NET
#14Jeff Atwood talks about moving from .NET to Ruby for Discourse in 'Why Ruby?'
http://www.codinghorror.com/blog/2013/03/why-ruby.html
Boiled down to the licensing of the requirements to run the stack, and the whole open-sourceness of it all.
Re: Why I Moved Away From Microsoft ASP.NET
#15ASP.NET is a great tool. If you were to walk into a gig that has a large amount of apps running VS, IIS and SQL Server, its no way you'd even suggest full blown open source. If things were reversed and all they had was Django, Apache and MySQL then of course you'd be a unwise to suggest moving to ASP.NET. I think as programmers we forget we must constantly use the information presented to make the best decision on which tool to use.
IMHO - Your article should read more like your customer base has changed, thus your tools have changed.
Re: Why I Moved Away From Microsoft ASP.NET
#16I'm coming from a classic ASP background as well, and jumped straight to MVC (skipping Web Form entirely).
Only later when I did some WPF project, when Web Forms made some sense. I think the whole toolset is basically trying to lure / accommodate the old Win Forms developer to switch to the web (and in this sense, it's a great success).
These days, I'm trying to run even leaner by using ServiceStack.Razor, as most of the stuff I do is service-oriented SPAs.
Re: Why I Moved Away From Microsoft ASP.NET
#17> The vast majority of .NET projects involve working with giant, monolithic, boring, poorly written, legacy “enterprise” products. These products always seem to be 4-8 years old and 2-3 major platform releases behind the current .NET framework To be fair this can be said for pretty much any project written in pretty much any language or framework.
Couldn't agree more. If you want to develop in cutting edge technologies for your weeks-old startup then code away and enjoy living on the edge (with all of it's pros and cons). But almost everything else (not just enterprise) lags behind and for good (many) reason(s). I work for clients and while I'm tempted to offer new technologies, I'm aware that this client will be using this tool for years, most likely as-is. S…
There's a difference between using a brand-new Node.JS framework that's barely out of alpha and using Rails/Django/etc which whilst fairly new are proven to be stable and reliable, and are in use at big organisations.
Re: Why I Moved Away From Microsoft ASP.NET
#18I moved to C# from Java back in 2001 for the RAD projects I had (still using C++ a lot when necessary though.) C# was a great language and it was faster than Java back then. But for the last couple of years all my RAD projects are now in JavaScript and it wouldn't go back.
JavaScript frees me up, where as with C# I feel like I am in a straightjacket where I am forced to write a lot of boilerplate code just to do something quick (a simple Main requires a class to exist!)
Re: Why I Moved Away From Microsoft ASP.NET
#19> The vast majority of .NET projects involve working with giant, monolithic, boring, poorly written, legacy “enterprise” products. These products always seem to be 4-8 years old and 2-3 major platform releases behind the current .NET framework To be fair this can be said for pretty much any project written in pretty much any language or framework.
"Boring" is pretty safe when it comes to quality and maintainability.
Re: Why I Moved Away From Microsoft ASP.NET
#20Jeff Atwood talks about moving from .NET to Ruby for Discourse in 'Why Ruby?' http://www.codinghorror.com/blog/2013/03/why-ruby.html Boiled down to the licensing of the requirements to run the stack, and the whole open-sourceness of it all.
I would love to run mono in production, it's just so slow and buggy that this isn't possible.
The simple fact is that server is not a priority for xamarin; mobile is. And this is probably a valid optimization.
BizSpark helps though, as far as licensing issues goes.