3 ms·
I have a different opinion. When we moved from the old way to semantical HTML5 generated still server side but which the layout was defined by the finally matur
by antirez 6y ago
I have a different opinion. When we moved from the old way to semantical HTML5 generated still server side but which the layout was defined by the finally mature CSS, with the dynamic parts handed by JavaScript and RPCs, everybody agreed it was better. Such web was faster, more compatible, simpler to parse, and so forth. I think that, if in the 20 years that followed, frontend development would progress in the same direction of improvements, everybody would agree again now.
And indeed everybody agrees that JavaScript itself is now better as it is the modern web APIs. If the rest is so controversial there must be a reason.
- arcturus17 6y agoI’ve heard and read stories from seasoned engineers, here on HN and elsewhere, that say that FE dev was as prone to tire fires back then as it is now, so I don’t think that point is as incontrovertible as you claim it to be. Some of those seasoned old-school engineers have, believe it or not, embraced modern FE frameworks and architectures and wouldn’t go back to the old thing if you paid them to do so. I’ve seen testimonials here on HN and surely it must be a factor in the world moving in this direction - it was not the juniors who made these decisions after all.
- antirez 6y agoMy point is different: I said that true evolution from tables to create the layout, continuos refreshes of the page to update the state, to a better development environment was universally recognized. And if it was again a case of good design, everybody would see it. If many voices are talking about over engineering now I bet there is a reason.