<grammar fanboy>In this article Lee quotes the Light Table demo as saying that it was accomplished with "with just a few lines of CSS and JavaScript," and then remarks that "I was curious as to the contents of those 3 lines as they must be the most powerful 3 lines of code ever written. In actual fact, the JavaScript file that drives the demo is 700 lines long."
What in god's name makes people assume that "a few" means "three?" "A few" just means exactly what it says: a relatively small number. Two is actually a relatively small number in certain circumstances, so you could say "a few" to mean "two." In this circumstance, 700 lines of code could be said to be "a few" lines, because I've seen full Javascript apps that use 7000 lines.
I don't really care about the trivial Flash/HTML5 contentiousness, and I'd rather stay out of it. But I keep encountering these weird misapprehensions based on imaginary rules concerning the phrase "a few," and it seems silly to me. </grammar fanboy>
You may be a "grammar fanboy", but I don't think your proposed semantics of "a few" are necessarily correct.
What I was commenting on was the apparent accretions of personal "rules" surrounding the use of the phrase "a few" colloquially. Sure, when I say "I cooked a few eggs," there's a context; people know I wouldn't cook 7000 eggs, so they would never assume that's what I meant. But I have in fact been chided by people pedantically when I've said something like "I cooked a few eggs," meaning two; in this case, people have often said to me that what I really mean is that I cooked a couple eggs, as "a few" is apparently distinct from "a couple."
All I'm saying is: there aren't necessarily little rules governing when people can and can't use the phrase "a few." I object whenever I'm told that I really shouldn't use "a few" to mean "a relatively small amount;" why not? Maybe Apple's mention of "a few lines of CSS and Javascript" in the article really does imply only and exactly three, but I can't see how. It's possible that there are agreed-upon linguistic usages that mean that Apple is actually lying, but it seems to me much more likely that "a few" is just a phrase that's more fluid and less strict than Lee is taking it to be. Chiding people for using "a few" to mean "relatively few" rather than "always and only three" seems silly to me.
Think about how people use the term. "I'm having a few people over for a bbq." Or "I ate a few cookies." Would you ever expect to see 700 people at the bbq or that the person ate 700 cookies? I think if you were to ask people "how many is 'a few'?" The answer would likely be a number greater than 1 and less than 10. Or maybe a range within 1 and 10.
But is there any honest argument at all that these demos, regardless of how letter-of-the-law standards compliant they actually are, are not categorically more open, standardized, and web-centric than Flash?
Moreover, if you don’t like the Safari UI you can check out one of several Webkit browsers (most notably Chrome).
If you could do everything with emerging web standards that you can now do with Flash this wouldn’t even be a contest. The emerging standards would win hands down. You admittedly can’t (yet?) but it really does look as though the scenarios where you need to use Flash are getting scarcer by the day.
Apple might be the bad guys with respect to the App Store, they are the good guys as far as browser development is concerned.
Also, being hardware accelerated on OS X, Safari renders 2D/3D transitions at superior framerate compared to Chrome (don't even mention Firefox). The difference is huge. Apple's message is "Hey look, we made a great (open source) rendering engine and want show you what can be done in HTML/CSS when things are properly implemented. Check this out as a reference implementation and feel free to implement it in your browser."
[Yes, the 2D/3D HW accelerated rendering uses Apple's proprietary frameworks and is not open sourced, AFAIK.]
This new state of affairs saddens me somewhat as I have always liked and respected Apple and they are now giving me cause to doubt them.
