4 ms·

This is a common rebuttal against any dissent against the insane flux of the front end space and I genuinely don’t believe that anyone with significant experien

This is a common rebuttal against any dissent against the insane flux of the front end space and I genuinely don’t believe that anyone with significant experience in software actually believes it. The front end space is really quite unique in its fragmentation and pace of change. Things are…maybe starting to cool down a touch, but not really. We can talk til the cows come home about how this or that have caused things to be how they are, but simply chalking this up to “things change fast in tech” - beyond just being a thought-terminating ‘shrug your shoulders’ platitude that I’d probably hear from a non-tech family member over Christmas lunch - is really missing most of what’s going on here.

b112 4y ago
Front end doesn't change that much from an implementation and coding perspective. To that I mean, if you could code 5 years ago, and deploy a front end of any sort 5 years ago, you won't have many issues today. People still use redis/memcached, mysql, php, apache2, with laravel for example. And solutions such as docker, with unvetted builds snagged from random people, are no different, functionally, than a VM or even a bare metal cluster. I will agree that the absurd node ecosystem, with its unsecure, unauditable packages, composer and its insane web of just stupid dependancies are ridiculous. But that's not rapid change of method or coding language, just because behind the scenes it's all just language such as php. So sure, the cruft is just that, but the meat is what drives change, and a lot of it.