7 ms·
The founder of Leptos makes a pretty good argument [1] that the bottleneck for WASM isn't really the DOM and that they are already faster than some popular JS f
by jbjohns 2y ago
The founder of Leptos makes a pretty good argument [1] that the bottleneck for WASM isn't really the DOM and that they are already faster than some popular JS frameworks even with the current constraints.
[1] https://youtu.be/4KtotxNAwME?si=IEZ5kRHR_W2o9i_k https://youtu.be/4KtotxNAwME?si=IEZ5kRHR_W2o9i_k
- pjmlp 2y agoJust tried the site, and already the first problem is isn't as interactive as the Websites for any JavaScript framework, because naturally there is a whole contraption to make the code run into the browser.
- jbjohns 2y agoThat's odd. I have been following along here [1] and it seems just as interactive as Svelte, Angular or any of the others I've tried. There might be a few more tools that have to be installed, but that's a one time step. [1] https://book.leptos.dev/01_introduction.html https://book.leptos.dev/01_introduction.html
- pjmlp 2y agoStill doesn't look like it, this is the kind of interactivity I expect. https://react.dev/learn/tutorial-tic-tac-toe https://react.dev/learn/tutorial-tic-tac-toe Where editing the code, immediately shows the GUI related changes on the neighbouring frame. While what I see on https://leptos.dev/ https://leptos.dev/ is just screenshots, and there is nothing on that documentation you linked that provides the same interactive experience, one has to explicitly start a developer sandbox to host the whole machinery, and even requires a codebox account for editing.