4 ms·
That's because "modern javascript" is not there yet, it's still in an experimental phase, we need transpilers and other stuff to use features that are not in a
by kowdermeister 10y ago
That's because "modern javascript" is not there yet, it's still in an experimental phase, we need transpilers and other stuff to use features that are not in a finished state. It will get better with time.
- inimino 10y agoAnd that getting better process is what people mean by reducing fragmentation.
- papyrus23 10y agoYou're literally contradicting yourself. "It's not there" i.e its a stinking pile of shit.
- ldehaan 10y agothat's not correct, and he did address why it doesn't suck. because it's not standardized. some people do better with more complicated things, it's ok to need directions, not everyone does.
- boggydepot 10y agoyour sentences fit in that blog post about a conversation with someone who wanted to build a simple web app in jquery
- monocasa 10y agoSo when is Javascript not going to be in an experimental phase? A couple of years ago it would have been 'when browsers support ES6'. Now it's 'when browsers support ES7'. Next year it's going to be 'when browsers support ES8'.
- irrational 10y agoTo be fair, ES6 was huge. ES7, and probably ES8, are tiny by comparison with only a few new features. Once browser creators get caught up on ES6 it _shouldn't_ be too hard to stay caught up after that point. But, most of experimentation isn't around the core ECMA features. The experimentation is happening around the toolchain, the libraries, the frameworks, etc. which are separate from stuff like ES6.