4 ms·
From personal experience, you probably want Babel anyway even with TS to deal with some weird edge cases. I think this has been fixed now. But a couple of week
by NhanH 10y ago
From personal experience, you probably want Babel anyway even with TS to deal with some weird edge cases.
I think this has been fixed now. But a couple of weeks ago, I had a case where TS compiler output has to be ES6 (since the code base were using something like constructor.name which isn't in ES5), but then Jest (the test framework) doesn't like ES6 syntax, so Babel is needed to compile whatever Jest didn't like down to just ES5 syntax.
- baq 10y agowebassembly can't come soon enough. as a developer who doesn't deal with browser frontends what i read in this thread is madness. (3 comments at the time of writing this...)
- nol13 10y agoit's like they don't even realize how ridiculous this shit sounds..
- rplst8 10y agoI don't think the point of WebAssembly is to target the DOM. I think it it's to provide a common low level API across browsers that many languages can target.
- nol13 10y agoSorry was referring to the infinite layers of transpiling and sub-languages that people talk about like it's normal, which I admittedly get why they exist, but it's still fucked. But that too. (though maybe wasm + canvas will let someone eventually implement a decent ui toolkit? Think I saw at least one attempt at this.) Current project could maybe benefit from TypeScript, and certainly async/await, but still wonder if it's less of a hassle to just wait for wider support.
- nol13 10y ago..and no i dont want to use VS Code either! grumble grumble grumble (Of course if yc ever decides to fund our small startup it should know that we are a team of forward thinking progressive individuals who will use the best and most robust tools available to us, who's views i do not necessarily represent)
- themihai 10y agoWASM is supposed to be first class citizen so I don't see any reason why it shouldn't have access to the DOM or any other browser feature available to JS.
- spankalee 10y agoWASM doesn't have DOM access or GC. It's not the answer.
- denisanerson 10y agoI read that DOM access is not available at the moment, but is planned for future releases.
- SiVal 10y agoIs that correct? WASM has no DOM access? (I'm asking, not advocating anything.) How does code that runs in a browser do UI I/O without DOM access? Is the intent that you go on writing all of your I/O and DOM-manipulating code with JavaScript and call WASM-implemented helper functions from JS code?
- markdog12 10y agoNo DOM access for the MVP. They do plan on eventually supporting it though: https://github.com/WebAssembly/design/blob/master/FutureFeatures.md https://github.com/WebAssembly/design/blob/master/FutureFeat...
- themihai 10y agoI think we can hack a reverse js proxy before it gets native DOM access.
- smitherfield 10y agoInside a <canvas>/<object>/<embed> tag.
- friendlygrammar 10y agoIn the first release it wont have DOM access or GC
- facepalm 10y agolol