we've

This creates fragmentation and a jungle of compile-to-JavaScript languages order of magnitude bigger than what we've got now.

So I don't think we've got a resource problem, but again all of these are back of the envelope numbers I'm just throwing out there.

We're a small team, growing fast, and already taking a big bite out of Craigslist's juicy NYC revenues, but we've set our sights on much bigger goals.

It took another few years before we got EGA - and then, finally VGA - graphics, which we've all become very accustomed to in this day and age.

It's used so heavily, that the river does not run to the ocean any more and the resevoirs we've been using the river to fill up are at historical lows.

- We've written a container stack which we offer on-premise and as a PaaS.

Proficient in: * Python ['django', 'bottle', 'google.app.engine', 'pyramid'] * Javascript ['angular','backbone','node','firebase']; * Clojure '(compojure liberator) * Go {'appengine'} * Haskell, Prolog (and other esoterics) We've helped entrepreneurs develop their MVP, as well as large companies develop core features.

While there is always power in this sort of "yeah, we've always said that and always been wrong!" argument, I still feel that the benefits of computing "power" have slowed to a crawl recently.

We've raised $427k on Kickstarter, doubled our team in our new downtown office, and have a great investor network.

We've taken Jason Fried's TED talk [1] to heart and built an entirely distributed team, which includes even our CEO.

We've hired people from these threads with everywhere from 0 to 10 years of experience.