The most popular and well-known one is Babel - compiler implementing the latest and greatest ES-Next (a term for all new and up-coming ES versions) features ASAP and most likely a good friend of yours. This works almost all the time for new syntactic sugar but not really for modern language features and API, but it's enough to satisfy the needs of many developers. These transpilers (term used interchangeably, but in my opinion better-describing the purpose of these tools) just take the code written in modern-style and change it to one compatible with more older browsers.
That's why the JS compilers were created. So, not everybody wants to wait this amount of time just to experience easier, better and modern coding solutions. Old browsers' versions obviously will never get new features and on the newer ones, it may take a long time to implement them. Naturally, the fact that the standard has been defined, doesn't mean that it will be implemented right away. V8 from Google Chrome) and this is where things start to get less fun. But ECMAScript is just a standard that needs to be implemented by different browsers' JS engines (e.g. It also greatly impacted the JS ecosystem with frameworks like Angular, React and Vue becoming even more popular and dependent on. async / await) in a yearly release cycle. ES2016 (ES7), ES2017 and up only made it better with even more features (e.g. With added functionality and some syntactic sugar, it made the web a place for more and more advanced websites and web apps. Just face it - ES6 made JS fun to write again. Do you - probably a JS developer reading this article right know - remember ECMAScript 6 (ES6)? Released in 2015 ES6 standard for JavaScript language is what kick-started JS rapid development that can be appreciated today.
0 kommentar(er)
