Boring Technology Debate

I personally find that most developers (especially those in a web related field) tend to shift to newer technologies when there is very little reason to do so, and perhaps more importantly, be an evangelical today. Ask yourself this: do you seriously think that a company would benefit from switching stacks every few years, or sticking with a mature and battletested technology?

No, because you can't expect to learn and use every new technology - sometimes, it's better to know "proven but boring" than "new but broken"!I appreciate more the insightful conversations than view a link to the latest JavaScript framework.

Some similar articles and threads:- Choose Boring Technology: http://mcfunley.com/choose-boring-technology, comments at https://news.ycombinator.com/item?id=9291215- Chasing the Shiny and New: h

It's very reasonable for someone new. It's batshit insane for anyone who's been in the industry for about 20 years. But that doesn't matter. The only thing that does matter is finding tech that you're productive with, and you've found it, so everyone else's input is pretty moot. In addition, it sounds like you've found the right idea anyway which is: avoid complicating work.It's a real tangible accomplishment to find a tech stack you're produc

I'm a bit old myself, I can share the same feeling and what I would call my "base tools" have been stable for more than 20 years now. But I don't have a problem adopting "new things", as long as they solve problems I actually have. If you're turned off by what is shown in the video, maybe that's just because this framework does not solve anything for you. Another reason could be that it does not fit well in your current, battle-tested, stack. Let the new g

I don't understand what's so difficult about holding the following facts in your head at once:1. Better tools make you more productive and make larger problems tractable. Using outdated or subpar tools seriously limits your options, especially if you need to compete with professionals. The simpler your problems, the less this matters.2. It's easy to get sucked in to constantly learning the new language/framework/toolset when you enjoy learning these things, finding the balance between the

I think it's mostly because the new tech Solves-A-Problem-That-I-Recognize, and developers mislead themselves into thinking the new tech is does everything old tech does, plus this, and they downplay the trade-offs being made (or they aren't experienced enough to recognize the tradeoffs).

It's like everything else in the JS world. A new solution to a solved problem. It takes more than an incremental improvement to outweigh the learning curve and development costs. New things should be an order of magnitude better. If a new technology isn't obviously better then it should be ignored. Developers have shiny object syndrome.

To some extent, that is true regarding my personal preferences, but being in tech and writing code for over 20 years teaches you a few things. Developers should be more picky about tools they adopt without becoming too cynical or dismissive of new technology. Every so often you have to go through your technology shed and be sure you aren't being biased towards existing comfortable tools. It's nice to work out of your comfort zone and learn new things, but it's also nice to be very

What's your point? We should just not try out new things? It's not like HN is representative of the industry as a whole anyway. Platforms, languages, frameworks etc etc learn and copy from each other, imo people switching technologies are helping these processes.