Chapter 1. You Can’t Afford to Avoid ES6
ECMAScript 6 is a big deal. ECMAScript, everyone’s favorite scripting API, hasn’t had an update this significant since it was initially formalized. Some people may feel overwhelmed as they browse through the impressive list of new features. Each was carefully considered, discussed at length, and selected for adoption into the official API. Ours is the task of rolling out these new features, bringing ES6 to our teams and to our projects.
But exactly how are we do that? How do we take these new features and concepts and infuse them into the brains of our developers? How can we inject this new power into our current projects? Just as important, and possibly more so, is when should we do this?
You may feel that you can’t afford to implement these features in your world. Some of you may prove yourselves to be extremely talented as creating reasons why you can’t afford it at this time. I am here to tell you that you can’t afford not to. As you read on, consider yourself warned: the content that follows is highly controversial.
Note
While the main audience of this book is composed of development management, I am sure that a handful of developers will find their way here as well. If you are a developer, welcome! If you are in management, I hope that you enjoy the ride.
The remaining sections in this chapter will cover various reasons for adopting ES6 into your current and future projects. Although not a complete list of reasons, it should help ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access