4 ms·
It’s probably about time for that to become fashionable again
by kyleee 1y ago
It’s probably about time for that to become fashionable again
- ChocolateGod 1y agoIIRC its what frameworks like Svelte do when they hit the compiler and optimize, which makes the best of both worlds.
- wruza 1y agoThey still nail "state" to element trees, which creates unbenchmarkable but real update costs. Svelte does better than react, but only within the same paradigm.
- MrJohz 1y agoCan you describe what you mean by that a bit more? As I understand it, with the new signals-based system in Svelte, updating data directly updates the DOM.
- division_by_0 1y agoIt's also worth noting that the Svelte signals implementation is quite performant. [0] [0] https://github.com/sveltejs/svelte/discussions/13277 https://github.com/sveltejs/svelte/discussions/13277
- JoeyJoJoJr 1y agoDo you mean subscribing to events/callbacks, manually managing object lifecycle, manually inserting list elements, keeping it in sync with the state, etc, etc. Because that was all friggen horrible. Maybe new approaches could make it less horrible, but there is no way I’d go back to what it was like before React. If anything, I want everything to be more reactive, more like immediate mode rendering.
- vendiddy 1y agoIt's easy to forget how tedious things used to be before React became popular. Keeping data in sync with the UI was a huge mental burden even with relatively simple UIs. I have no desire to go back to that.