3 ms·
What are features for if we don't use them 8-) Not all features increase complexity. The fat arrow functions are more easy to reason about as "this" can be und
by heisenbit 10y ago
What are features for if we don't use them 8-)
Not all features increase complexity. The fat arrow functions are more easy to reason about as "this" can be understood more locally. When transpiling the code may be larger but in the long run maintainability should be better.
I found the Crockfords talks on ES6 (e.g. https://www.youtube.com/watch?v=vJKDh4UEXhw https://www.youtube.com/watch?v=vJKDh4UEXhw) useful as a guidance what could be a minimal set of sane features.
- sAbakumoff 10y agoI agree. I love ES6 in fact. The fat arrows really rock. I like how I can use them together with promises to write a concise code like create_project(prj_name).then(project=>addTeam(project, team_name)).then(team=>addMember(team,name)) The main point of the article was in that using new JS features blindly may cause the significant problems, not with readability, but with the script size and the running time of the code after it’s transplied to ES5.