[esskay]

I had a similar situation a year or two ago and since then have had several juniors complain that we're using "old tech" or missing out on the latest packages.

I gave up trying to be understanding and reason with them. It just seems new developers, and especially frontend developers see a shiny new package every week and want to try it. Before we put a stop to it we were lumped with a handful of projects that were frankly awful, with a bunch of spaghetti javascript code written in the flavor of the week which wouldn't compile on anything except a very specific version of a bunch of packages, whilst pulling in close to a gigabyte of random dependancies that nobody had any kind of handle on from a security point of view.

[felipemnoa]

So the moral of the story is that you should be using old timers to write your code? They've seen it all and no longer are impressed by the shiny new thing. All they care about is making it work and most importantly: being productive.

[datavirtue]

Adults should be present and in charge, yes.

[zaphirplane]

The thing is a library usually advertises how they address a painful experience in other projects. That is the hello world fallacy, there is a blog about it.

Basically you see how elegant or easy to do X in a new library but you don’t see how complicated it is to do Y. Y is complex in the new library and simple in your existing library