1,301 karma · joined November 17, 2008
I know that I find more mistakes in my code when time reveals the code as it is rather than as it was intended. But I can't say this makes me good enough at proofreading myself. What about the code I've conceived and written in ignorance?
If H.264 support is being removed to “enable open innovation”, will Flash Player support be dropped as well? If not, why?
The premise is that openness is all or nothing. But Google can support Flash and work towards openness, just as Apple can prefer open web standards in lieu of Flash while supporting proprietary systems. There's no hypocrisy or conflict.
Android currently supports H.264. Will this support be removed from Android?
Maybe in the future. WebM support is new in Android, hardware decoders are really just coming to market, and there are enough existing and in-production phones that rely on H.264. The constraints placed on Google by the handful of Chrome users leveraging H.264 HTML5 video is completely unlike the realities of dealing in the handset market.
YouTube uses H.264 to encode video. Presumably, YouTube will be re-encoding its entire library using WebM. When this happens, will YouTube’s support for H.264 be dropped, to “enable open innovation”?
YouTube continues to support other proprietary formats. As with Sorenson, they're not going to drop H.264 until they don't care about the market share of H.264-only devices. In the meantime, they will try to drive people towards WebM in support of "open innovation". This is not inconsistent or even new.
Do you expect companies like Netflix, Amazon, Vimeo, Major League Baseball, and anyone else who currently streams H.264 to dual-encode all of their video using WebM?
It should be obvious that Google's hope is anyone using HTML5 video will eventually move to WebM exclusively.
If not, how will Chrome users watch this content other than by resorting to Flash Player’s support for H.264 playback?
Content producers won't care if Chrome users end up in Flash, since the content's still available and very few non-mobile users are getting HTML5 video anyway. Flash is still the norm outside of mobile devices.
Who is happy about this?
Were people ecstatic that Chrome supported H.264? Most people simply don't care about this kind of stuff and for good reason.
The worst part is that I have no idea what benefits schemas are supposed to bring me. The documentation vaguely promises that schemas "can drive more intelligent processing", but I have a feeling I could get that more easily without schemas. It also tells me that "explicit types eliminate the need for guessing of types," but only, apparently, by requiring users to understand and remember them.
$"test";
It turns out that '$' can only operate on an identifier or another '$' expression. The '${...}' syntax, aside from being more readable and less likely to be accidentally encountered, is more like an operator: ${"test"}; // equivalent to $test
The decision to keep (and only warn against) unescaped strings past the introduction of an incompatible feature (constants) is inexcusable. It creates oddities: $test = 'foo';
$foo = 42;
echo $test . " ${test} " . ${test} . " " . $$test . "\n";
This generates a notice and prints, "foo foo foo 42". But then: $test = 'foo';
$foo = 42;
define('test', 'foo');
echo $test . " ${test} " . ${test} . " " . $$test . "\n";
This will print, "foo foo 42 42". (Note also the difference between the meaning of ${...} within string interpolation versus outside of it.) Is this all understandable? Sure. Is it good? No.I see this fallacious reasoning all the time in design critiques: this is inconsistent with that. Well, yes, but so what? Why is consistency desirable in this instance?
That's a small piece of the picture. With partitioning, a move could entail removing data from one table and inserting it into another. With sharding, a move could mean removing the data from one database and inserting it into another, which probably means manually ensuring consistency because your typical transaction won't span databases.
Now consider that Basecamp allows comments on messages, todo items, and milestones. What does your schema look like now? Add a feature to show a user all recent comments across all of his projects. What does your query look like? How does it perform? Get all of this (not to mention the other features) working at scale.
Maybe you can build something like Basecamp that works at Basecamp's scale without resorting to denormalization, sharding, and/or partitioning. But I doubt it.
@weby.template()
def index(W):
with W.html():
with W.head():
W.title('Hello, world')
with W.body():
W.h1('Hello, world')
W.p('Lorem ipsum dolor sit amet')
with W.ul():
W.li('Lorem')
W.li('Ipsum')
W.li('Dolor')
with W.div(className='footer'):
W.p('foo bar baz bim')
A smaller win is to use keyword arguments (instead of passing a dict).That's abject nonsense. Intentionally offending people doesn't make them grow up. It makes them feel aggrieved.
Also, the blue bar might work better if it spanned the entire width of the right column and fixed to the top of the content area. Right now, because of the content that appears above it and all the white-space to the right of it, it feels like it's floating over and blocking content.