Hacker News Reader

Comment by chollida1 | Hacker News Reader

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

View on HN

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.

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.

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.

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 :)

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.

So often the line is when the business owner has spent enough money to feel more comfortable with their technology choice.

Re-read what josefresco said - because this is the reality.

"Boring" is pretty safe when it comes to quality and maintainability.

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.

It's also called job security - there's a lot of old crap to clean up no matter what the language.

Reply on news.ycombinator.com