News for hackers. Stuff that matters.
Re:Why I Moved Away From Microsoft ASP.NET by chollida1 on Monday September 23, 2013 @08:19AM (#6430311)
> 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 by josefresco on Monday September 23, 2013 @08:31AM (#6430345)
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 by 300bps on Monday September 23, 2013 @09:05AM (#6430548)
Stability, maintainability and long term investment is many time more important than gee-whiz tech.

I'll add one more: Googlibility. I don't like to use bleeding edge technology because when I google error messages I get nothing back.

Re:Why I Moved Away From Microsoft ASP.NET by kaolinite on Monday September 23, 2013 @08:41AM (#6430383)
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.
Re:Why I Moved Away From Microsoft ASP.NET by josefresco on Monday September 23, 2013 @08:54AM (#6430468)
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 by gizzlon on Monday September 23, 2013 @09:38AM (#6430737)
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 by josefresco on Monday September 23, 2013 @11:29AM (#6431590)
I wasn't specifically using Ruby as an example of new/unstable tech. My point was that your average business owner doesn't know Ruby from ASP from Perl. It becomes the job of the tech provider to implement technology that not only serves the need now, but also the need years down the road.
Re:Why I Moved Away From Microsoft ASP.NET by airwot4 on Monday September 23, 2013 @09:03AM (#6430536)
So often the line is when the business owner has spent enough money to feel more comfortable with their technology choice.
Re:Why I Moved Away From Microsoft ASP.NET by robodale on Monday September 23, 2013 @09:19AM (#6430632)
Re-read what josefresco said - because this is the reality.
Re:Why I Moved Away From Microsoft ASP.NET by scrabble on Monday September 23, 2013 @08:42AM (#6430396)
"Boring" is pretty safe when it comes to quality and maintainability.
Re:Why I Moved Away From Microsoft ASP.NET by weblivz on Monday September 23, 2013 @08:56AM (#6430476)
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 by quaffapint on Monday September 23, 2013 @08:26AM (#6430329)
It's also called job security - there's a lot of old crap to clean up no matter what the language.