Re:Glimmer.js: What’s the Deal with TypeScript?
by recursive on Thursday April 13, 2017 @11:30AM
(#14107809)
My complaints about JS have nothing to do with the DOM. Like weird `this`, no integer types, surprising type coercion rules, and so forth.
Re:Glimmer.js: What’s the Deal with TypeScript?
by bauerd on Thursday April 13, 2017 @06:01PM
(#14111241)
>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?
Re:Glimmer.js: What’s the Deal with TypeScript?
by pryelluw on Thursday April 13, 2017 @10:43AM
(#14107352)
What would you replace the DOM with?
Re:Glimmer.js: What’s the Deal with TypeScript?
by untog on Thursday April 13, 2017 @11:16AM
(#14107676)
I 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.
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.