News for hackers. Stuff that matters.
Re:Why Ageism Never Gets Old by ams6110 on Thursday November 16, 2017 @09:12AM (#15712702)
> Not only is the claim "now it’s five years at most, and, for a software engineer, less than three" an unhelpful mythology, it's laughably incorrect

It's narrowly referring to the "framework fads" that do seem to sweep through our profession on about a three-to-five-year cycle.

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.
Re:Why Ageism Never Gets Old by skrebbel on Thursday November 16, 2017 @10:51AM (#15713630)
Going off topic fast, but I've felt recently that this speed has slowed again.

On the frontend, React has been king for quite a long time now, with no obvious contender in sight. Of course there's stuff like Vue but the difference isn't so big that people are throwing away their gigantic React codebases to restart anew with Vue (things that did happen a lot with jquery, bootstrap and even angular based frontends). The new kids on the block may be better, but only by a relatively small margin.

Similarly on the backend, Rails has been unfashionable for quite a while now, but there's no obvious single new framework that people are flocking to. Sure, there's many hip options, like Elixir/Phoenix, vanilla Go, and bunch of "serverless" frameworks, but just as many people just start their new projects on Rails, Laravel, and ExpressJS, because that shit is productive and it just works.

I feel like, decades after the desktop UI world, the web as a platform has pretty much matured. The core concepts aren't changing that much anymore. I think that maybe something fundamentally new has to happen again for this cycle to truly restart - just like the web as a software platform was once fundamentally new. We'll get new programmers who can reinvent all these ideas again in confusingly subtly different ways. It'll be fun!

Re:Why Ageism Never Gets Old by arethuza on Thursday November 16, 2017 @12:27PM (#15714556)
I suspect WebAssembly may provide the start to that new cycle you are (or are not) looking forward to.