hasancc

I like the idea of bringing the academia closer to the developers. Let's face it, with the wave of coding bootcamps etc. there are a lot of developers without the STEM background needed for sophisticated applications. I think that this vision can present a lot more opportunities for interesting products. It may also speed up the pipeline from the academia to the deployed application.

Or perhaps there are physical constrains like the durability. On pebble's website it does mention being scratch resistant but I don't know if it can endure the frequent impact it will encounter in many sports.

I agree. An open bracelet would be cool but from a bussiness point of view it doesn't make that much sense. There are countless of startups who refused to focus on a core target market and failed. Instead what you should do is focus your development efforts on the core product and listen to community feedback for cool ideas, then provide the necessary API for them to build it. Which is basically what these guys are doing.

Mind = Blown! One of the most exciting stories I read on the internet. Not only the story is awesome, the writing also stands out. Kudos to the author: Zachary R. Mider.

Yes Chrome is event driven, but Chrome is a sandbox which limits your I/O capabilities. Node.js on the other hand, is obviusly not a browser, so you can actually do I/Os with the system not only the sandbox.

neither. It just uses v8 to execute the interpreter output which is still javascript code.

V8 converts javascript to machine code, and node.js basically acts as a middle man to add functionality to javascript like "event driven programming" which can't be implemented through a basic framework.

I've been using it for quite a while now. I'm ashamed to say that it's simplistic approach on collections often made me question the urgency of writing API documentation when developing a private API. Why not just send the collection of examples? Well, we all know why but still...