Skip to main content

Benjamin Oakes

Photo of Ben Oakes

Hi, I'm Ben Oakes and this is my geek blog. Currently, I'm a Ruby/JavaScript Developer at Liaison. Previously, I was a Developer at Continuity and Hedgeye, a Research Assistant in the Early Social Cognition Lab at Yale University and a student at the University of Iowa. I also organize, ICRuby, OpenHack Iowa City, and previously organized NewHaven.rb. I have an amazing wife named Danielle Oakes.

Filtering for the JavaScript category. Clear


by Ben

BrowserFS is an in-browser filesystem that emulates the Node JS filesystem API and supports storing and retrieving files from various backends.

Source: jvilk/BrowserFS


by Ben

An extremely fast, React-like JavaScript library for building modern user interfaces

Source: infernojs/inferno

Factorisation Diagrams

by Ben

Factorisation Diagrams – Jason Davies

The prime numbers really stand out. Made with D3.js.

Node v7.0 is out! It holds such promise… :D

by Ben


Vanilla List: The Vanilla Javascript Repository

by Ben

Coz’ sometimes you feel guilty for using jQuery.

No dependencies.

Source: Vanilla List: The Vanilla Javascript Repository


by Ben

A modern approach to copy text to clipboard. No Flash. No dependencies. Just 3kb gzipped

Source: clipboard.js

ember-concurrency: structured concurrency in JavaScript

by Ben

Escape from callback hell in JavaScript, but with cancellation. Excellent visualizations.

Example code:

export default Ember.Component.extend({

  myTask: task(waitAMoment).drop(),


Also interesting: enqueue

Source: EcPrezo

#NodeJS : A quick optimization advice

by Ben

Can you spot the difference between these two files that can explain a 50% performance gain?

Source: #NodeJS : A quick optimization advice

Wow. But please don’t optimize for comment length prematurely.

Found via the JavaScript Slack channel.

Miscellaneous JavaScript Reading

by Ben

Some JavaScript reading I’ve been doing since Iowa Code Camp last week:

On Asm.js

by Ben

On Asm.js —

A great perspective on the role of JavaScript in the future of the web. I don’t agree with all of it, but it’s certainly true that asm.js still feels like a clever hack, perhaps taken too far.

The ASCII/UTF-8 comparison to JavaScript/asm.js is something I hadn’t considered. That’s even more telling when you realize that ASCII has its roots in telegrams… Where will JavaScript be 100 years from now?