Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why I Moved Away From Microsoft ASP.NET

ryanbennett.com

Post reply on HN
Print view View original

61–70 of 110 posts

Re: Why I Moved Away From Microsoft ASP.NET

#61

Post by gizzlon »

josefresco wrote: post #32
kaolinite wrote: post #17

Earlier quoted context omitted.

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

Is Ruby going to be around in 5 years?

Ruby (the language) and rails (the web-framework) are not the latest fads to come out. Rails hit 1.0 in 2005, a.k.a. almost 8 years ago, ruby is much older.

Although there can be good reasons to choose something new, I agree with your overall sentiment. But we seem to have extremely different views on what constitutes "new"(node might qualify :)

Re: Why I Moved Away From Microsoft ASP.NET

#62

Post by SonicSoul »

ASP.NET is a decade+ old technology. It made lots of sense when it came out (state management across postbacks, flexible caching, full base class library, completely extensible object model). combined with early ajax frameworks, we did some great things with it back then (like in browser live stock trading apps before GMail was out) with relative ease..

now there are lots of alternatives.. this is equivalent to writing a post about "why i got off windows 98"..

Re: Why I Moved Away From Microsoft ASP.NET

#63

Post by hrasyid »

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…

maybe it was down because it uses ASP.NET?

Re: Why I Moved Away From Microsoft ASP.NET

#64

Post by NKCSS »

twistedpair wrote: post #60
NKCSS wrote: 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 ViewState should be encrypted with the MachineKey[1] of the server and shouldn't allow you to decrypt it if they store sensitive data in it, but at least one control needs to request for the encryption or have the encryption set to always [2]

[1] http://msdn.microsoft.com/en-us/library/w8h3skw9(v=vs.85).as...

[2] http://msdn.microsoft.com/en-us/library/aa479501.aspx

Re: Why I Moved Away From Microsoft ASP.NET

#65

Post by rnbennett »

hrasyid wrote: post #63
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…

maybe it was down because it uses ASP.NET?

Unfortunately because I'm cheap and I am using the smallest Linode plan available. Don't normally get this kind of traffic...

Re: Why I Moved Away From Microsoft ASP.NET

#66

Post by nmeofthestate »

swalsh wrote: post #59
nmeofthestate wrote: post #41

Earlier quoted context omitted.

"today WPF is all but discontinued" This is an interesting claim - WPF is still the main UI framework for writing Desktop apps, right? I don't know of any replacement framework that is preferred by MS for authoring desktop apps (I never use any WinStore apps on my Windows 8 devices).

I went to BUILD in June, and attended an overview of what's new in XAML. After the talk, I went up to the guy, and I was like "Wow there's a lot of cool things going on in XAML, how much of this do we get in WPF?" His reply was basically, all of the visual studio enhancements will come to me. However the new controls etc will not. He said WPF is in maintenance mode only for now.

It seems understandable - they have limited resources and have a lot of work to do on their new WinPhone and WinStore platforms.

So, not a flurry of cutting-edge development, but very much not deprecated either.

Re: Why I Moved Away From Microsoft ASP.NET

#67

Post by pmarsh »

spongle wrote: post #56
300bps wrote: 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…

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.

Re: Why I Moved Away From Microsoft ASP.NET

#68

Post by leeohsheeus »

nmeofthestate wrote: post #41
swalsh wrote: post #22

Earlier quoted context omitted.

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

"today WPF is all but discontinued" This is an interesting claim - WPF is still the main UI framework for writing Desktop apps, right? I don't know of any replacement framework that is preferred by MS for authoring desktop apps (I never use any WinStore apps on my Windows 8 devices).

There hasn't been a significant upgrade to WPF in years. Microsoft's stance seems to be that "desktop apps" should not be a thing any more - there weren't any WPF sessions at Build, for example.

Re: Why I Moved Away From Microsoft ASP.NET

#69

Post by corresation »

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…

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.

Re: Why I Moved Away From Microsoft ASP.NET

#70

Post by Touche »

spongle wrote: post #56
300bps wrote: 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…

Ditto on Razor. It's like 2002 php. Except you can't really create reusable partials because of static typing. Sure, you can just make everything dynamic, but then the top of your view turns into:

   @{
     /* A bunch of repetitive object creation and casting */
   }
Which has happened in every razor project I've seen anyways.
Post reply on HN