News for hackers. Stuff that matters.
Re:JavaScript hydration is a workaround, not a solution by solardev on Friday September 02, 2022 @01:03AM (#32686793)
And sorry, one more thought: Canvas work can itself be abstracted with frameworks like OpenLayers or PixiJs or Unity. It's a testament to how powerful browsers have become that you can run full MMORPGs or other games in the browser. But that all depends on being able to download a huge Javascript bundle at load time, but then the rest of the experience is usually pretty smooth.

Games and maps are just an extreme version of that, but other examples where clientside DOM apps with heavy JS can still be faster (compared to old school server-side HTML) and easier to work with (compared to canvas) are email, e-commerce, ebooks, dashboards, chat, forums, video tubes, search and filtering, galleries, documentation, project management, etc.

Re:JavaScript hydration is a workaround, not a solution by remexre on Friday September 02, 2022 @06:59PM (#32696685)
I can see email and chat, sure, but ebooks, forums, video tubes, and documentation? All four of those seem like they shouldn't require much JS, and I would be unsurprised to find good examples of each that work even with JavaScript disabled.
Re:JavaScript hydration is a workaround, not a solution by solardev on Saturday September 03, 2022 @10:46AM (#32702339)
Sorry, the threads got a little confusing here. I think this particular one was discussing those examples in the context of using Canvas vs HTML, with or without Javascript.