The real reason to avoid jQuery

Or How to avoid common SPA pitfalls when using 3rd party plugins This is a cross post of blog post I wrote and published for IsleOfCode on January 26, 2016 here. In the past few years, I've read countless blog posts, twitter rants and medium exposés detailing how jQuery isn't necessary, and why you should just write with "native" JavaScript. I disagree with these posts, because there are still a number things which jQuery handles which are not easy to replicate quickly unless you know the edge cases you need to handle. There is, however, a very major reason to avoid jQuery, and it has very l…

Read more »

Using WebWorkers to bring native app best practices to javascript SPAs

Posted on

Do you remember when jQuery exploded? Suddenly it seemed that for every feature you might want on your website, there was a jQuery plugin. All you had to do was include the script tag, and you were golden. If you do much front-end development these days, you may have realized that the days of "just drop in a script tag" will soon be over, if they aren't already. While jQuery brought about a revolution in Javascript usage, the front end still lacked organized code, dependency management, and the build tools required to ensure optimized web assets. This transition –away from script tags and in…

Read more »

Managing ordered child components in Ember and Glimmer

Posted on

In the quest for native quality HTML5 apps with Ember, I started building smoke-and-mirrors, the core concept of which was to build a set of highly performant reusable components for use in applications that needed to optimize rendering. The primary feature is the occlusion-collection, a highly optimized alternative to listView or ember-cloaking. Interestingly, it's implementation details are fairly similar to ionic's new collection component, which in past iterations was more similar to listView. Ionic apparently reached some of the same conclusions on performance and native scrolling. Pre-…

Read more »

Reclaiming the URL from ember-data

Posted on

It's great that ember-data 1.0 is coming. It's long overdue. But lest you get lulled into thinking that ember-data 1.0 is a finalized product, it's time to take a step back and look where it's deficient and at everything it's missing. The adapter pattern is amazing. Produce a highly standardized thing (A), provide an interface for connecting it to any other thing (C), and add an easy ability to write an adapter (B) that connects the two. End result? Some serious magic. The new Macbook doesn't have X port A cheap adapter connects you to anything, and in a few years as technology progress…

Read more »