Re:The Planned Obsolescence of Old Coders
by james_s_tayler on Friday March 08, 2019 @09:07PM
(#19344019)
Yup. And when you chime in with "wait for it..." you get the nasty vitriolic comments thrown at you like you're going to rot in the basement of a fortune 10 feeding a legacy system while the $cool_kids enjoy the sunshine on the beach with their new shiny frameworks.
Yet "Wait for it" usually turns out to be correct.
That's pure gold. Not to say there haven't been advances--there certainly have been. But, there's also the issue of the shininess of new tech giving it undue cred, while simultaneously translating to an outsized denigration of the tech it purports to replace.
Frankly, a lot of these problems have been solved, and solved well.
Look at NoSQL as an example. There are certainly use cases for it, but then people went nuts, exclaiming things like "RDBMS must die" and touting no ACID transactions as a feature/benefit. Then, you get the trickle of reports that maybe NoSQL wasn't the best choice for this or that.
Finally, fast-forward to 2018 and you have announcements from MongoDB that they now support ACID transactions.
Many older coders have seen enough of these cycles, and have adopted a justifiably-cynical posture of "wait for it...".