4 ms·
They're already using JavaScript for all new code, and gradually converting their existing code over using decaffeinate (e.g. https://github.com/atom/atom/commi
by alangpierce 9y ago
They're already using JavaScript for all new code, and gradually converting their existing code over using decaffeinate (e.g. https://github.com/atom/atom/commit/30cd83f7aa03c023e6103b648906107796472fe8 https://github.com/atom/atom/commit/30cd83f7aa03c023e6103b64... ). But it's a reasonably big codebase and I imagine moving everything over incrementally will take a while.
- baby 9y agoWhat about moving to web assembly? Would it be relevant? Or is this a Firefox feature only? Or is this not interesting because the point is to write it in javascript?
- alangpierce 9y agoWebAssembly will be supported by all browsers and JS engines, but it's not something you would use as your source code. I think at the moment it's more focused on high-performance use cases, e.g. rewriting a CPU-intensive function in C++, compiling it to WebAssembly, and calling it from your JS code. Or taking an existing C++ codebase and running it on the web without really using the DOM. But in the long run, I think WebAssembly will make it possible to do things like DOM interactions in other programming languages.
- treyhuffine 9y agoThere was actually a huge consensus on the direction of Web Assembly recently. https://medium.com/@treyhuffine/coding-news-monthly-summary-a2fd77df9e9 https://medium.com/@treyhuffine/coding-news-monthly-summary-...