Why I Moved Away From Microsoft ASP.NET

Post by nmeofthestate » Mon, Sep 23, 2013, 1:02 PM UTC

swalsh wrote: post #22

untog wrote: post #13

Earlier quoted context omitted.

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.

> they already use MS all the time Exactly, we've been the bread and butter for Microsoft for a long time. Yet with Windows 8, we're starting to feel like that's just not true... at least that's the sentiment when I talk to some of my colleagues. For instance We built our main product using WPF, today WPF is all but discontinued. XAML is bigger then ever, but only if you want to make a windows store app. If I leave .…

Post by 300bps » Mon, Sep 23, 2013, 1:05 PM UTC

josefresco wrote: post #7

chollida1 wrote: post #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.

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…

Post by idProQuo » Mon, Sep 23, 2013, 1:08 PM UTC

redact207 wrote: post #25

Tried 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…

Post by untog » Mon, Sep 23, 2013, 1:12 PM UTC

ehmuidifici wrote: post #39

untog wrote: post #4

I 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…

Post by hhandoko » Mon, Sep 23, 2013, 1:16 PM UTC

daigoba66 wrote: post #38

The 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 licensin…