3 ms·
> writing to future standards that are not supported by the current underlying interpreter. What is the problem here? You can't expect billions of browsers to
by mekster 7y ago
> writing to future standards that are not supported by the current underlying interpreter.
What is the problem here?
You can't expect billions of browsers to be updated so soon and I'd be hairless if I still had to write in ES5 just because there are still IE out there.
Currently I favor in writing TypeScript but if Ruby Next starts supporting type hinting for Ruby 3, then I'd like to give it a go as soon as possible which can even be deployed on current environment. The only problem would be the lack of editor support for the new syntax.