Miller Medeiros

A unbaised post comparing the two would be nice. Sounds like a post Addy Osmani would write. I found this post(http://blog.millermedeiros.com/amd-is-better-for-the-web-than-commonjs-modules/) talking about why the author thinks AMD is more flexible (better). Though a biased article(though I think the CJS approach to defining an AMD method is reasonable), it does show the syntax of the two approaches. I CJS syntax has less boilerplate, but is that due to fact that CJS loads synchronously? YES, I know processors like Onejs can make so CJS modules can be used in a browser(wonder is the processed result looks similiar to Requirejs?). Just wondering if Requirejs is designed the way it is because it took loading modules asynchronously into account from the begining.

>I think the big difference here is that Apple is actually right. Flash on mobile is terrible for battery life and its implementations, so far, are shoddy.

What about HTML5 and Apple's promises? It's been a while since Jobs wrote that and still Apple's HTML5 implementation is not up to par. http://blog.millermedeiros.com/2011/01/ipad-is-the-new-ie6/

On top of that, Apple is in no hurry to bring the speed improvements of their Nitro JS engine to apps pinned to the homescreen. After all, they prefer devs to make native apps so that there is a lockin.

>There's a big difference on imposing your will over 25% of the market versus 96% of the market. Apple has nowhere near the power Microsoft did

What about tablets where Apple is deemed to have 94% of the market?

Nice tutorial, I just disagree on two small points.

First, there are very sound arguments for not using CSS preprocessors [1].

Second, for a website that you own, using ".htaccess" is discouraged for performances reasons. The Apache 2.4 docs [2] say:

"You should avoid using .htaccess files completely if you have access to httpd main server config file. Using .htaccess files slows down your Apache http server. Any directive that you can include in a .htaccess file is better set in a Directory block, as it will have the same effect with better performance."

[1] http://blog.millermedeiros.com/the-problem-with-css-pre-processors/
[2] http://httpd.apache.org/docs/2.4/howto/htaccess.html

> For example, he took a lot of flack here for defending Apple's move to leave flash out of mobile safari

It's been much more than a year since Steve's blog post about how Flash is unneeded because of HTML5, and I am still waiting for the improvements in Safari so that Flash like functionality can be used in web pages. http://www.apple.com/hotnews/thoughts-on-flash/

I am not holding my breath though, Apple wants to push developers towards apps and not web pages, because they get to make money on every sale and also because it creates a lock-in for their platform.

http://blog.millermedeiros.com/2011/01/ipad-is-the-new-ie6/

The point is to get better results for the same effort.

Instead of having to spend time styling the top bar and tab bar to look native, and battling with fixed positions and mobile browser inconsistencies, you just drop a line into your config.

Many people seem to think fixed position elements and dealing with scrolling in mobile web views is a pain:
http://bradfrostweb.com/blog/mobile/fixed-position/
http://www.kylejlarson.com/blog/2011/fixed-elements-and-scrolling-divs-in-ios-5/
http://blog.millermedeiros.com/ipad-is-the-new-ie6/