Timmy_C

It's three sections on one page. There's nowhere to navigate. You don't even leave the page to log in. I don't know how you're lost.

This is a killer HTML/CSS boilerplate. It's clean and simple and does just enough to get a responsive layout up-and-running.

Coderwall does give you links to contact the author if you'd like to suggest something. His Twitter handle is on his profile page.

If you live in Seattle you'll see WP7 phones in the wild. They're all owned by Microsoft employees however.

I remember that when Backbone came on the scene, not having to use native elements was a selling point. If you wanted to use native elements you could. But you'd end up having to put `event.preventDefault();` in every one of your event handlers.

You're right. I guess I was trying to use the list icons.

It uses inline styles. That's an issue for me. It also looks like it doesn't do nested lists.

On the other hand, full-screen mode is really cool.

I think this is the article you were thinking about.

http://blogs.msdn.com/b/b8/archive/2011/08/26/improvements-i...

The interesting part is that CSS variables are inherited unlike in SCSS/SASS. That means you'll have to assign all your variables to ancestor nodes if you want to reuse them everywhere on the page.

I can see the `:root` selector getting pretty crowded with variable declarations.

The argument he makes is that it boils down to maturity. One framework is still evolving and the other is more mature.

No IE7/8 support because it doesn't do CSS generated content or the :before and :after pseudo-elements.

I think you should fork it and rewrite the CSS for the dashboard. The markup for the code snippets is just <pre> elements. You could set the white-space to 'pre-line' for those elements to take care of the width issue.

I looks like most of the inline JavaScript is there to handle DOM abstraction and events. Every click essentially needs to be able to build a part of the page client-side.

I keep seeing comments here about whether-or-not consumers are using their iPhones and iPads to do word processing and spreadsheets. And I think that argument misses the point that the article was trying to make. I think the conclusion was that we don't need spreadsheets and word processors at all. There are a lot of tools out there that help you "get business done" that are not focused around typing a document or generating a chart. I get business done by using Freshbooks and Balsamiq Mock-ups.

I don't see why they made commands like copy and paste into buttons. It seems like they could simplify their interface by using more conventions and fewer ribbon buttons.

I tend to dislike the ribbon in general because it feels like their designing software for the user who likes to click things and not for the user that uses keyboard shortcuts.

I think I did really poorly. My score was around 21,000.

You'll end up "fixing" the same thing more than once. Not very DRY.

It looks like all the comments here are from SEOmoz employees.

Why do you use more than one? I thought the point was that you could sign in once with your OpenID and be signed in everywhere.

These are just the browser stats for this site and I see your point. However, the article is implying that there is going to be a trend toward browser apps in the future and Firefox does not have a built-in browser app platform.

Chrome apps get downloaded to your machine. They are not links.

The Chrome apps he's talking about get downloaded to your machine then run in the browser as if they were a webpage on the net. I'm guessing that Internet Explorer 9 has a similar feature but Firefox doesn't have anything like this on the roadmap.

This article argues that apps are the only future for browsers and by virtue of the fact that Firefox doesn't have a dedicated "app ecosystem" it will be extinct.

I don't follow the reasoning since I don't really see why I have to use Internet Explorer to use a Microsoft web app just as I don't have to use Chrome in order to get my Gmail.

margin: auto;

The best part of this article, for me, was the link to letscrate.com.

It's not bad. I like the simple design of it.

The previous logo had some details that got lost at smaller resolutions and the icon itself was kind of a nondescript colorful futuristic object. This one looks more like an icon and doesn't leave me asking, "What is it?"

True, those aren't exactly the harshest critiques.

You obviously stopped reading after the first page.

The second page of this article points out a lot of features that Microsoft FINALLY got around to implementing and some of the short-comings that are still lingering. If I remember correct, the last couple paragraphs claim that Firefox 4 or Chrome will pass up IE on features in the near near future. Not exactly a PR plant at that point.

You can apply styling to the :first-letter pseudo element but that's where it ends.

It's silly not to use a bundler with Rails (both for JS and CSS). That way you don't incur the performance hit from organizing project files by controller name.