Here is an alternative Piped link(s):
piped.video/4KtotxNAwME?si=D_vWV1LPQI-C9j8G
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source, check me out at GitHub.
Comment on Are we ready for javascript without a build step on the front end in 2023?
icesentry@programming.dev 1 year agoThat’s actually a myth and real world performance isn’t affected by this. See this video from leptos creator which is one of the more popular wasm ui framework youtu.be/4KtotxNAwME?si=D_vWV1LPQI-C9j8G
The biggest issue is actually the size of the payload since you need to ship the entire app and language runtime.
PipedLinkBot@feddit.rocks [bot] 1 year ago
jvisick@programming.dev 1 year ago
It’s not a question of performance - it’s just the fact that you need to use JS to modify the DOM in WASM. Until there is access to the DOM from WASM, there simply will be a place for JS in nearly every web app and it’s not because it’s fast, it’s because there are still certain things just need to be done using JS.
My point is really nothing to do with performance and I agree with the video you’ve linked: WASM is fast enough today. Whenever you can truly stop using JavaScript, I’ll be the first in line. You can already use WASM and eliminate huge portions of JS - but for anything beyond a very simple UI, you always end up with something that needs to be called in JS.
icesentry@programming.dev 1 year ago
I mean, I get what you’re saying but with rust all that js code is auto generated and you can make a full app without writing a single line of js yourself.
jeremyparker@programming.dev 1 year ago
Isn’t that why god made HTMX? Jokingly asked, but legitimate question - I don’t know much about WASM’s reach - and I can’t seem to watch that video on the train. Could HTMX (+/- hyperscript) take it from there?
jvisick@programming.dev 1 year ago
You could do HTMX and WASM, but they both have the same problem in that they generally replace elements in the DOM as opposed to interacting with existing elements in the DOM, and most rendering on both HTMX and WASM actually happens through JavaScript calls.
In either case you’re limited to only interact with the DOM at the level of abstraction that the framework provides through “behind the scenes” JavaScript calls which will always be a subset of the DOM manipulation that is possible by directly using JS. At least, until there’s a standard DOM access API for WASM.
jeremyparker@programming.dev 1 year ago
I keep trying to find a way to play with a web dev stack that doesn’t involve JavaScript, but I think that might be a pipe dream…