I’m reading this New Yorker story on George Holtz.
It’s nice.
I want to add it to instapaper.
I’m on a ferry to the Brooklyn Ikea.
So I google search for the article on my mobile phone – with the intension of saving it to instapaper.

Two problems:

This is not a sustainable process. I’ll only really do this for articles I really, really want to remember. But, hey, at least I finally found my first good need for a QR code.

The New Yorker site sent me to their m.newyorker.com version of the article.

I hate mobile websites. I mean, I love being able to read a site on my non-laptop/desktop device (NLDD?) but I hate m.*.com sites. I won’t say they break the web… even though they just might… but they certainly break my process. You can’t build the web to think it knows better than you do. This is the equivalent of those car radios that turn themselves down when you slow your car speed. And that’s for old people.

There are so many reasons that your website should be responsive to the device that it is being shown on. This is just one of many.

If Twitter’s CSS framework Bootstrap actually catches on, it will go a long way to unite the web and let us move on to more important problems.

Much like how jQuery has turned knowing JavaScript into just having to know a certain level of JavaScript, Bootstrap will be a common foundation for everyone writing CSS.

So, for example, you could have a bland WordPress theme that is written on a foundation of Bootstrap (eager to see how this goes.) that users could customize with a separate css file that is loaded after.

With tools like Bootstrap, our time spent on startup that used to take the first three or five hours of a project may now be up and running in five minutes. Which is good, because we’ll need that extra time to deal with Responsive Design/Development.