C#, Linq, MVC, Web Api, reasons I still use the platform. I did web forms for a few years and there is no way I would be using it today. Thankfully MVC came around.
Why I Moved Away From Microsoft ASP.NET
31–40 of 110 posts
Re: Why I Moved Away From Microsoft ASP.NET
#32Earlier quoted context omitted.
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.
I agree, however there is no defining line for the non-tech savvy that determines what is bleeding edge, and what isn't. Is Ruby going to be around in 5 years? If Ruby is around, will I be able to hire developers easily and for a reasonable price? These are concerns that drive businesses for whom tech is a necessity but not the core of their business.
So the business owner relies on the tech provider who hopefully isn't in a full on romance with the newest framework/language just because it's new.
Re: Why I Moved Away From Microsoft ASP.NET
#33> 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.
I completely agree with you. One could interpret that line as a "scalable", "proven" and "stable" technology framework.
People should focus on integration between components - the argument between language and frameworks died many years ago.
Re: Why I Moved Away From Microsoft ASP.NET
#34The modern Microsoft stack is pretty good. MVC + Razor, Entity Framework + Linq. It compares very well to modern web stacks like rails, or django and then some. And then you get use tools around MSSQL like any business intelligence tools.
The VS MVC templates in vs 2013, come with bootstrap preinstalled which shows the general direction they're going in now.
Re: Why I Moved Away From Microsoft ASP.NET
#35Cached version: http://webcache.googleusercontent.com/search?q=cache:http://...
Hmm, a few visitors and Ryan's blog has crashed. What non-Microsoft tools & hosting do you think he used?
Re: Why I Moved Away From Microsoft ASP.NET
#36Most of the time the top article goes down. However there is always gooogle cache: http://webcache.googleusercontent.com/search?q=cache:U8pNBnR...
Re: Why I Moved Away From Microsoft ASP.NET
#37> 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
While it's fun to make fun of a 25 year's seemingly rash decisions, sometimes those youngsters' rush to embrace a new language or tech actually does move business forward where before it would not have.
Re: Why I Moved Away From Microsoft ASP.NET
#38The only decent argument against anything in the Microsoft stack, in my opinion, is the licensing costs. You pretty much need to develop on Windows using Visual Studio. And for ASP.NET you pretty much need to deploy to IIS on Windows Server. Though at scale the OS and MSDN licensing costs can be just a drop in the bucket. That is until you decide to use SQL Server on the backend. It's a great product but the licensing costs can make you go broke. If I started a new product or company and used .NET and needed an relational database I would seriously consider PostgreSQL.
Re: Why I Moved Away From Microsoft ASP.NET
#39I 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…
A few years ago, I participated on a interview for a job (in a startup) which requires some skills in ASP.NET.
When I started talking to company owner and I said to him that I knew PHP (and ASP.NET too, of course), he started to say that ASP.NET is better
because it's paid, expensive and it has a great support from Microsoft... That's all he said about it.
Later on, I discovered that almost 7/10 of big companies' IT managers think the same, that's why ASP.NET still has its audience.
The same goes on with Oracle.
Re: Why I Moved Away From Microsoft ASP.NET
#40Tried reading this but the site was down... ironically. I've been developing the .NET stack for 10 years now and would have to say straight ASP.NET is the easiest way to add the most horrible amount of bloat to your pages and bring about horrible performance. My gut feel is that it was made to allow application developers to build intranet sites without having to worry about the stateless nature of HTTP. The result w…
I'm with you. I think it's funny how people put down a technology (ASP.NET) that was released in January of 2002 because it's not up to snuff with 2013 web development tools.
I also made the switch to ASP.NET MVC and can't imagine ever going back to ASP.NET. The unbelievable clean HTML you get, full control over rendering and rapid development is just phenomenal.
Most of the anti-Microsoft comments I see on HN are of the "but VB6 is terrible!" and "ASP.NET stinks!" variety from people that stopped looking at Microsoft development tools over a decade ago and are still comparing those old tools to their modern competitors.