JavaScript hydration is a workaround, not a solution

Re:JavaScript hydration is a workaround, not a solution by sopooneo on Thursday September 01, 2022 @11:06AM (#32677402)

I remember when HTML5 and CSS3 were just in the RFC phase and many web developers thought they would make their jobs simpler. Because the things they were being asked to do, for which they were currently creating tortured workarounds, could be done directly with the new standards.

But of course the job did not become simpler. The fixed value turned out not to be what clients would demand, but the quantity of tortured workarounds devs could be enticed to endure.

[ Parent | on HN ]

Re:JavaScript hydration is a workaround, not a solution by mattwad on Thursday September 01, 2022 @12:04PM (#32678430)

I'll be an anecdote: I literally only came back because of CSS3 and jQuery. Managing layout with tables and all hover effects with javascript did not sound like a fun career choice when I first started. And now I've fully embraced flexbox and grid and styled components - I rarely have to think about classes anymore. New tools have been making my job a lot more fun over the years.

[ Parent | on HN ]

Re:JavaScript hydration is a workaround, not a solution by hypertele-Xii on Thursday September 01, 2022 @11:58AM (#32678334)

Almost got back into webdev but the technical interview was 100% JavaScript.

[ Parent | on HN ]