News for hackers. Stuff that matters.
Re:React Router v4 FAQ by wyager on Friday September 16, 2016 @12:49AM (#12511907)
Probably PHP and plain JS, which is why I think that argument doesn't make sense. New web stuff is currently so much better than the old alternative that dealing with tumultuous stability is often worth it.
Re:React Router v4 FAQ by tomca32 on Friday September 16, 2016 @01:07AM (#12511969)
I think there's a middle road. What you're mentioning is pretty extreme. Rails/Django/Spring and Angular/Ember are all considered boring and very stable while not nearly as outdated as your example.
Re:React Router v4 FAQ by wpietri on Friday September 16, 2016 @12:02PM (#12514935)
Care to show me your math on that over a 10-year time scale?

I'd be curious even to see it for the technologies you mention. But as others point out, there are plenty of things newer than PHP that have become pretty boring.

Re:React Router v4 FAQ by HereBeBeasties on Friday September 16, 2016 @03:21AM (#12512428)
Is it? I used to happily make very complex sites using Apache Wicket on top of Java. It lets you make composable, extensible components (including inherited markup). It is type safe (the cools kids are finally rediscovering how important this is for maintainability with Flow & TypeScript). It supports replacing components using AJAX. Sure, it's not great for client-side SVG rendering or the various other cool things you can do with React and co, but hand on heart, I can't honestly say I find doing all this stuff in JavaScript to be "so much better". Quite the opposite for the majority of intranet-type sites, in fact.