Live data from Hacker News

Why I Moved Away From Microsoft ASP.NET

ryanbennett.com

81–90 of 110 posts

Re: Why I Moved Away From Microsoft ASP.NET

#81

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…

MVC4 with AngularJS Why combine a server-side MVC with a client-side MVC? Honestly the ASP.NET MVC advocacy doesn't make sense to me. It is a solution that half brings .NET developers into the modern era. Using it purely as a service layer is that project essentially trying to maintain relevance in the face of irrelevance.

Yep, half-way sounds about right. By default ASP.NET doesn't allow you to GET json, have to override that.

Also the routing is not RESTful at all and doesn't handle nesting very well, so you have to find a 3rd party routing library or role your own.

Re: Why I Moved Away From Microsoft ASP.NET

#82
post #28

His thoughts on ASP.NET WebForms are just; it's a piece of crap trying to make websites have state and you should stay away from it as far as possible. I am a .NET developer like the poster, also been with the framework since the first beta (doing not just web, but also windows development), and I've had my share of frustrations with ASP.NET WebForms as well, but I quickly noticed that I could use Generic handlers (.…

Was accessing a very slow HMO site yesterday. Peeked at the source and most of the wait was for the 800K ViewState string. Wasn't that hard to decrypt either. I think that is the source of most anti-ASP.Net sentiment.

The first outsourcing disaster I experienced was view state related. Back in 2003, a membership management app I inherited managed to hang of view state. Each page would throw 2.5Mb across a LAN. It sucked. It also had numerous bad patterns like UI driven SELECT N+1 hell. This is the norm for your average cheap custom build asp.net app.

We rewrote the entire thing in php (nice php!!) in three days and it's still used to this day without modification (even managed to get through a couple of security audits unmodified).

Re: Why I Moved Away From Microsoft ASP.NET

#83
post #47

Earlier quoted context omitted.

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…

They're not wrong, though. It's all about priorities. With an MS product you do get good support, and someone to shout at if something is not behaving as expected. With open source tech you can submit a patch to fix it yourself.

You sometimes get good support. I've spent too much time on the phone to then (as a gold partner) and got sod all back on most occasions. If you're lucky you get a workaround but most of the time it's denial.

Re: Why I Moved Away From Microsoft ASP.NET

#84
post #44

Earlier quoted context omitted.

Hmm, a few visitors and Ryan's blog has crashed. What non-Microsoft tools & hosting do you think he used?

It's hosted with Wordpress on Linode so you are correctly spotting a huge dose of irony.

Irony Indeed! Never see traffic like this usually.

Re: Why I Moved Away From Microsoft ASP.NET

#85
post #56
post #40

Earlier quoted context omitted.

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…

Sorry signed up to say this - been lurking a while but this one infuriated me terribly. The only reason ASP.Net MVC looks good is because you were a WebForms user before. If you've come from other tech, it's still a stinking pile of crap. 1. The API is totally broken and consists of tonnes of barely testable wrappers (HttpResponseWrapper etc). 2. The attribute model is a pain in the arse. How do you test filters base…

Sorry, signed up to say that you sound like an angry young developer. It sounds like you're angry that you're being "forced" to use a tool you have no idea how to use. I use many different development frameworks and have even used Visual Studio. It's not my main development environment but even I know enough not to load 34 projects into a single solution. Ever hear of compiling some of them and referencing the binaries? What a cluster your code must be.

Re: Why I Moved Away From Microsoft ASP.NET

#86
post #44

Earlier quoted context omitted.

It's hosted with Wordpress on Linode so you are correctly spotting a huge dose of irony.

I run Wordpress on an Amazon micro instance and have easily handled enormous runs without the server breaking a sweat or failing to serve a request. http://wordpress.org/plugins/w3-total-cache/ The simplest thing in the world.

It's kinda what I get for running Wordpress on Linode. I'll have to checkout AWS.

Re: Why I Moved Away From Microsoft ASP.NET

#89
post #73
post #67

Earlier quoted context omitted.

What extensions are you using with Visual Studio? Found vanilla to be really stable, but certain extensions result in some random crashes. But not terribly often.

None whatsoever. We killed R# and VisualSVN. Do without the former and use TSVN for the latter. We have 34 projects loaded in the solution so it hits VS's limited 32-bit process restrictions pretty quickly causing the debugger to break miserably. When this fails it's a restart job.

What do you need 34 assemblies for? Seriously?

Re: Why I Moved Away From Microsoft ASP.NET

#90
post #72

Earlier quoted context omitted.

I much prefer working in .NET MVC4 than I did trying the same pattern in Java with JSP/Servlet/Spring. Things seem to just work. As for 1, I haven't really had to write tests around these wrappers yet. I can't really comment on 2 as we don't use but a couple of pretty simple ones that ARE easily testable. I'm also really not sure what you mean with 3. If by "hint" you mean use @ as your denotation for C# code, then y…

Maybe you should update your Java skill? Servlet/JSP vs MVC4? Try SpringMVC and JAX-RS. I've ben going back and forth between Java and C# in the not-so-distant past and I felt that C# ecosystem is just too limited.

I mentioned Spring. It's been a couple of years, but doesn't Spring's MVC pattern use JSP for the view templates?
Post reply on HN