3 ms·
"So, to conclude: The future question will not be "why ruby?", but "why not javascript?"." Because you will be using TypeScript instead.
by _random_ 13y ago
"So, to conclude: The future question will not be "why ruby?", but "why not javascript?"."
Because you will be using TypeScript instead.
- anonyfox 13y agoWith "Javascript" i mean meta-languages that compile to javascript, too. I prefer coffee, but typescript may be fine, too.
- _random_ 13y agoReasonable, but that's a blurry line. If a meta-language gets traction it might get support for other compilation targets MSIL/bytecode etc.
- anonyfox 13y agoPossible. But since JS is already running on every desktop, smartphone, tablet and now on the server, why bother with less spread ecosystems? And, given that in some places already reaches half the performance of native code (which is incredible fast for non-c'ish code!), it should be fast enough.