4 ms·
I really hope we can see a unification of the efforts and work through the political issues. Having very talented developers working on separate codebases inste
by simplyluke 12y ago
I really hope we can see a unification of the efforts and work through the political issues. Having very talented developers working on separate codebases instead of improving one seems counterproductive.
- BinaryIdiot 12y agoThey have to merge otherwise one will die. There is no alternative. I hope it happens sooner rather than later.
- pekk 12y agoMultiple languages coexist. Within Javascript, there are multiple module systems, general utility/polyfill libraries, test runners... for better or worse, we continue to have many alternatives for almost anything. So why not also different implementations of a language interpreter?
- unknownian 12y agoBecause they run the same package manager and roughly do the same thing for the same purpose? It's not a JRuby vs Rubinius debate, imo; it's more like YARV vs MRI, you just don't need both. If they were more different I'd agree.
- BinaryIdiot 12y ago> Multiple languages coexist. Within Javascript, there are multiple module systems, general utility/polyfill libraries, test runners... for better or worse, we continue to have many alternatives for almost anything. So why not also different implementations of a language interpreter? As it was already said they run the same package manager and claim compatibility. This means you either can't take advantage of any new API in io.js ever to allow your module to work in both or you take the road where you're transpiling to support one and the other. It's not sustainable and it's prone to issues.
- pjmlp 12y agoWelcome to the wonderful world of writing portable C and C++ code across multiple compilers and OSs.
- deleted 12y ago[deleted]
- deleted 12y ago[deleted]