JavaScript gives us many ways to do things, but deciding which way can be tricky. Laurie Barth gives us a story of two experts who solve this problem in different ways, giving some insight into how to make these decisions for your team.
Topic: JavaScript
The behavioral layer. Progressive enhancement: creating sites that work on any browser or device, with or without JavaScript. Accessible scripting. Write less, do more with jQuery. Application Cache. Twitter Bootstrap. Adaptive design. Tabbed interfaces, collapsible elements, and accordion widgets. Modern debugging tips and tricks. A/B testing. Rapid prototyping with Sinatra. Popups and lightboxes and carousels, oh, my!
Now THAT’S What I Call Service Worker!
If you’re looking to achieve the single-page app level performance without the overhead (and boot time) of a huge JavaScript library or having to completely rewrite your website in a new technology, Jeremy Wagner shares a clever approach combining Service Worker and streamed web page partials you’re sure to love.
Responsible JavaScript: Part III
Convenience always comes at a price. On the web, developer convenience often means third-party JavaScript—and we pass the hefty cost on to our users. Jeremy Wagner shows us how to get and keep third-party scripts under control through clean-up sprints and eternal vigilance in Part III of Responsible JavaScript.
Responsible JavaScript: Part II
Web development is hard. We don’t always get it right on the first try. Fortunately, we don’t have to get everything perfect from the start. Jeremy Wagner provides some helpful ways to start recovering from our collective JavaScript hangover.
Responsible JavaScript: Part I
The web is drowning in a sea of JavaScript, awash with unnecessary bloat, inaccessible cruft, and unsustainable patterns. Jeremy Wagner plots a course to navigate the JavaScript Sea responsibly by building the right things the right way and using the web platform the way it was meant to be used.
Taming Data with JavaScript
Processing huge amounts of data on the web is always a back-end job—except when it’s not. Sometimes processing data in the browser via JavaScript makes sense. What are those use cases, and how can we succeed at them? Brian Greig tells all.
var to JIT
JavaScript language designer Kevin Smith completes the “From URL to Interactive” series. He explains how browsers compile and execute our JavaScript, and what happens from the moment we land on the page to when we leave. Understanding these browser processes leads us to write more performant code.
From URL to Interactive
When we think about it, our whole industry depends on our faith in a handful of “black boxes” few of us fully understand: browsers. We hand over our HTML, CSS, JavaScript, cross our fingers, and hope they render the experience we have in our heads. But knowing how they work can really get you out of a jam when things go wrong. That’s why we’ve assembled a handful of incredibly knowledgeable authors to take us under the hood in this four-part series. Join us on this trip across the web, into the often foggy valley between code and experience.
Coding with Clarity: Part II
Coding with clarity sets great developers apart from the rest. Brandon Gregory shares some principles for organizing objects and functions in JavaScript that will improve clarity, making your code easier to read, understand, and extend.
Fixing Variable Scope Issues with ECMAScript 6
Variable scope in JavaScript has always had its problems. ECMAScript 6 has some features to help developers deal with this and give them more control over their variables. Brandon Gregory gives the low-down on these features and when to use them.
