4 ms·
And I can't wait for the rude awakening anti-JS developers have when they realise the vast majority of issues (particularly, performance) come from the DOM, not
by untog 10y ago
And I can't wait for the rude awakening anti-JS developers have when they realise the vast majority of issues (particularly, performance) come from the DOM, not JavaScript. (And the first version of WebAssembly can't touch the DOM anyway)
If people start writing Python for the web for no other reason than they just dislike JavaScript we're going to be forcing users to download a dozen different runtimes, just because of developer preference. This isn't a good thing.
- pryelluw 10y agoWhat would you replace the DOM with?
- untog 10y agoI honestly have no idea. It does so much that I don't know where you'd start - but I suspect that's also the problem. I remember seeing a demo of React Canvas a few years ago - basically, recreating a "DOM" of sorts inside a canvas tag - and the performance was crazy. Beautiful 60fps touch interactions. But, of course, it only does a tiny subset of what the DOM does. I'm still waiting for a good reason to use it myself to try out how the API feels.
- pryelluw 10y agoI feel the same. Dunno wth we gonna do but we need something more performant.
- deleted 10y ago[deleted]
- recursive 10y agoMy complaints about JS have nothing to do with the DOM. Like weird `this`, no integer types, surprising type coercion rules, and so forth.
- deleted 10y ago[deleted]
- bauerd 10y ago>we're going to be forcing users to download a dozen different runtimes Why would users need to download a runtime, given that we'd have WASM as a compilation target for Python, the language?