JS Dialect Rant
Joey Mink Mar 29, 2017
Then I got started with React at my next job. Cool sh*t, no doubt. But ES5 components led to ES6 class-based components. When I tried to consume that ES6 code I would get invalid keyword errors on things like
import. Huh? transpile it with Babel! Oh, okay...
Then I got into mobx (<- totes dig it!), with all it's decorators and what not (oh Java, I do miss you a little). But when I tried to run that code, I'd get errors about
@ being totally uncool. Babel to the rescue!
- the state of the JS language
- the dialect you're writing in
- the translations that babel is performing (and how to configure it)
- interpreting the translation when debugging at runtime
Wowzers. I write JS, you may write JS, but I bet yours and mine look a helluvalot different. And I bet my code can't be pasted into your codebase without syntax errors. And to me, that's just kinda like ... woah.