mcastner

Here's the opposite side of the story with its own biases: http://scienceblogs.com/gregladen/2011/12/computers_of_crimi...

I preferred the lighter theme personally…

Just kill the process and delete the .app file. Compared to Windows malware this is a breeze to remove.

That's useful to see how something is done, but not why or the different options available. For that, there's still a definite lack of a clear guide. The guide on the Express website reads more like an API reference and doesn't go into detail on how to use the different features, which I think would be very helpful.

Right now I'm working on my first application using Express. Over the Summer, when I have free time, I'd like to write a tutorial series for Express and put it up on github so it can be updated as Express evolves. That's really one of the main issues right now, all this stuff is changing so rapidly that a tutorial can become outdated in a few months.

Just an example: they claim that Chrome "dropped support on Windows XP for functionality that [IE Team] think is fundamental to performance." Linking to this blog post: http://googlechromereleases.blogspot.com/2011/02/dev-channel...

The reality is that Chrome disabled it temporarily on the dev channel due to crashing, and in fact brought it back for v11: http://code.google.com/p/chromium/issues/detail?id=72975

Microsoft doesn't even acknowledge the fact that they don't even have a version of IE10, or even 9, for Windows XP!

Is this really what the browser wars are going to come to? Lies and marketing? I thought we were over that.

While you can write functions to create abbreviated versions of CSS properties, it's entirely optional.

Also I actually prefer Stylus' mixins and functions to SASS'.