THIS TUTORIAL HAS REQUIREMENTS AND INSTRUCTIONS LISTED BELOW
We’ve all heard it: “JS coercion is evil and bad!” It can seem so magical if you’ve never actually spent the time to understand how coercion works.
But this is definitely one of those places where you are doing yourself a disservice to follow the crowd hype. They’re all just as uninformed as you are, trust me!
In this workshop, we’re going to start from the ground up, understanding JS types, and look at the JS specification for authority on how coercion works. We’ll go through all the common culprits that get cited as “the bad parts”, and show why it’s all mostly just FUD.
Along the way, we’ll find the few legitimately bad/crazy parts, and some effective, simple rules for how to avoid those. But most importantly, we’re going to learn why coercion is not only something you should stop avoiding, but why it can actually improve your programs!
There will be plenty of code snippets for you to type along with, so come ready to code and coerce!
TUTORIAL REQUIREMENTS AND INSTRUCTIONS FOR ATTENDEES
Laptop with current/modern browser.
Comments on this page are now closed.
For exhibition and sponsorship opportunities, contact Sharon Cordesse at firstname.lastname@example.org
For information on trade opportunities with O'Reilly conferences, email email@example.com
For media-related inquiries, contact Maureen Jennings at firstname.lastname@example.org
View a complete list of Fluent contacts