Why I Moved Away From Microsoft ASP.NET
ryanbennett.com
Why I Moved Away From Microsoft ASP.NET
1–10 of 110 posts
Re: Why I Moved Away From Microsoft ASP.NET
#2> 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.
Re: Why I Moved Away From Microsoft ASP.NET
#3> 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.
It's also called job security - there's a lot of old crap to clean up no matter what the language.
Re: Why I Moved Away From Microsoft ASP.NET
#4I 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. Just with as little of the ASP.NET stuff as possible.
Re: Why I Moved Away From Microsoft ASP.NET
#5> Why I Moved Away From Microsoft ASP.NET
Because its almost 2014?
Re: Why I Moved Away From Microsoft ASP.NET
#6Cached version: http://webcache.googleusercontent.com/search?q=cache:http://...
Re: Why I Moved Away From Microsoft ASP.NET
#7> 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. Stability, maintainability and long term investment is many time more important than gee-whiz tech.
Re: Why I Moved Away From Microsoft ASP.NET
#8.NET certainly gets the brunt of the "it's not hip" posts. Yea, there's a lotta junk programs, because they make it easy for people to use in an enterprise. There's also a lot of junk java, etc.
That's why you play around on the side with all the new stuff. Using ASP.NET MVC lets you write much leaner html, without the need for all those controls, et al. They're releasing a lot of cool tools if you follow the blogs, and you can now just as easily create a clean bootstrapped page as you would in other offerings.
Re: Why I Moved Away From Microsoft ASP.NET
#9One 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 a refined platform, and the .NET framework is a joy to work with (personal opinion). Poorly written frameworks exist in any language, but there's also a lot of GREAT code written in .net too.
The platform is expensive, and that sucks... but we sell the product for 100k a pop... so frankly neither our customers or ourselves care about the cost. Developing quickly, and with the best quality possible is more important.
Re: Why I Moved Away From Microsoft ASP.NET
#10I 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.