On Github jpeterson / js-tooling-talk
Thanks for coming? :: brief-but-witty banter ::
I'm a developer at
I live in
I'm from
My name is Josh
I'm a developer here at Esri
Professional Services, build JS apps everyday
I currently live in Washington, DC and work in Esri's regional office there
But my home is the greatest place on earth: Colorado
Drinking game: 1. Come up with a noun or verb 2. Add a .js to your word and google it 3. If you found a library, drink
Now I'm going to briefly set up the demo by pinpointing some workflow problems solved by tools
Writing code - is there a "right" JS editor?
Yes and no. Find the editor that does what you need, keep in mind some were made for web development
Visual Studio and Eclipse are okay... but theres a lot of overhead and junk that you'll never use
Since JS doesn't compile until runtime, its hard to identify "pre-compilation" errors
Syntax errors, undefined variables, typos
For smaller JS projects you may not need dependency management
But as your projects grow in size, you'll be lost without it
To developers, CSS can be a bit of a curveball
It's not code, it can be very repetetive and theres a lot of typing and bloat
Now that we know all these great things we can and should be doing, how do we do them efficiently?
Did we just add a ton of effort to our workflow with each of these tools?
So thats the end of the build-up
We've identified a problem: "JavaScript is Hard"
We think we know why: Unopinionated Workflow, don't know what tools to use
Let's take a look at how some of these tools work...