4 ms·
Why do we? Assuming a need for interactive web content, what are our alternatives in pragmatic terms? 0)No scripts, each interaction is a round trip to the ser
by aww_dang 4y ago
Why do we? Assuming a need for interactive web content, what are our alternatives in pragmatic terms?
0)No scripts, each interaction is a round trip to the server
1)Minimally scripted pages with classic SSR
2)Full blown apps compiled to WASM and rendered on canvas
Even if we goto 2, we still have some minimal wrapper JS. I'm not sure we can escape it at this point. The best we can do is minimize our exposure.
- sophoskiaskile 4y agoI truly appreciate your time. But under today's world circumstances If we wanted to stick to the options we had. We would be still punching card for basic tasks. I'm seeking goal-oriented progression. If I want to be honest My question is a little bit more of a root-seeking question. I can not understand The urge for only using javascript in modern day web browsers. (BTW it was cool one starting your lists from 0 :))
- aww_dang 4y agoPerhaps the way forward is using the language of your choice as a WASM blob. If it becomes popular more tooling to expose the DOM directly to WASM will emerge. We still have the backend as a JS free zone.