3 ms·
It's going to be like java is now. You have to find the exact right date for the right runtime environment to get your JS to execute properly. And that is quite
by superkuh 5y ago
It's going to be like java is now. You have to find the exact right date for the right runtime environment to get your JS to execute properly. And that is quite a task. Complex toolkit JS is generally not forwards compatible for more than a couple years.
- brundolf 5y agoThat's... not remotely true. A built JS bundle consists of least-common-denominator JS that in theory should continue to run ad infinitum. "Don't break the web" is a mantra among browser devs. Rebuilding the bundle from scratch might be more complicated. But you don't need to do that to preserve it.
- sfink 5y agoUh... name one toolkit or platform or library that became incompatible with the JS engines after a couple of years? JS inherits the Web property of extreme backwards-compatibility. Breakages do happen, but they're extraordinarily rare. Unless you mean something different by compatibility? Sure, you won't be able to mix wildly different versions of libraries because their APIs change. But I wouldn't call that a "runtime environment".