The weblog of Bocoup, a web consultancy, with JavaScript posts on Backbone.js, Node.js, WebRTC, and Arduino programming.
HN commenters link it for specific JavaScript topics such as WebRTC in Opera Mobile, Backbone module organization, and random number generators in browsers.
I think you're slightly off with your conclusion of responsive web design. It doesn't aim to cater to people resizing their windows (that's just an added benefit), it aims to cater to all devices regardless of window size.
Assuming we're still considering responsive design, if designed from a mobile-first perspective you'd be surprised how clean the code can be to deal with this. Start with minimal resources and most of your content stacked vertically so that it's lightweight and easy to consume on a touch device. Providing you've used relative units (ems in particular) you can scale up for larger screen with super simple media queries that just bump the font-size on body (e.g. body { font-size: 120%; }). You can find an awesome overview of this approach on Trent Walton's site [1]. Compare this with a hacky approach of doing desktop-first - you're loading assets (probably) unnecessarily, hiding chunks of markup to never be displayed, hammering your CSS to fit your desktop peg into a mobile hole. I know this doesn't cover everything, and any sufficiently complex site will require more than just bumping font-size, but honestly it doesn't have to be super difficult and full of horrible workarounds.
Now with the resposnive vs. separate site debate, the way I've always thought of it is responsive site for web sites, separate sites for web apps. Apps are sufficiently complex, with enough interaction that they require fundamental changes in HTML, CSS and JS to adapt to touch…
If you're interested in Arduino and are familiar with js/node, check out Johnny-Five (https://github.com/rwldrn/johnny-five).
"My goal for Johnny-Five is to create a framework for programming Arduino Robots with nothing more then JavaScript. I believe that JavaScript, inherently asynchronous and the platform that Node.js has built around this paradigm, is the perfect environment for writing evented, streaming programs for controlling the highly synchronous world of hardware." -- via http://weblog.bocoup.com/javascript-arduino-programming-with-nodejs/
I don't know anything about robotics or arduinos (though I've done a bit of electronics hacking/tinkering throughout my life), but this project makes me want to jump right in head first.
"But really, an IL that doesn't support integers? An IL where a member field access may involve looking up a string in a hash table instead of being a single machine instruction? Propose that as an IL to a compiler guy and they'll laugh at you."
Yup, JS arrays look crazy when you are used to C and pointers (I was shocked when I first found out).
That's why WebGL folks had to come up with typed arrays:
https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/TypedArray-spec.html
http://weblog.bocoup.com/javascript-typed-arrays
Rwaldron has some good coverage of this over at http://weblog.bocoup.com/javascript-firefox-aurora-6-and-eventsource-api
Funny, I just posted this link to Rwaldron's coverage right before you posted to the link he is responding to.
Here's the "Organizing Your Backbone.js Application With Modules" article that was mentioned in the screencast:
http://weblog.bocoup.com/organizing-your-backbone-js-application-with-modules
One year ago I've seen demo's with Opera Mobile 12 and WebRTC
Found this linke: http://weblog.bocoup.com/javascript-webrtc-opera-mobile-12/