News for hackers. Stuff that matters.
Re:Why Ageism Never Gets Old by jerf on Thursday November 16, 2017 @10:11AM (#15713205)
Yes, but when Framework B goes sweeping through the world, Framework A doesn't actually go anywhere. People keep working with it.

If software engineers actually burned down all the old code every three years and literally everybody had to learn this new thing in order to do anything at all, this claim would make sense. But it's all additive. Even as we here on HN are shrieking and hooting about Framework B and the way it shines a unique light on the world of programming and how no thinking person could possibly resist its charms, thousands of people keep chugging along on Framework A for years afterwards. In no small part because they've heard it before, and remember that somewhere around the 2 year mark of Framework B's run you can expect well-written and cogent articles about "Framework B Considered Harmful", "Framework B Is Permanently Ruining An Entire Generation Of Programmers", "Why I'm Switching Back To Framework A And Regret Ever Listening To Hacker News" and "Oh Shit, I Bet My Business On Framework B And All My Developers Have Turned Into Feral Wombats And They're Biting Me Ow Ow Ow".

Re:Why Ageism Never Gets Old by rhizome on Thursday November 16, 2017 @05:10PM (#15717145)
Not to mention how much Java is written in Ruby, C written in Perl, and so on. Where the round-hole syntax of one language/framework can be hammered into the square-hole of another, it will be.