No, he just made a snide attempt to cast aside all criticisms of Blu-Ray inoperability as heresay without factual support.
BR has serious firmware and incompatibility issues that should be an embarrassment for all involved at this stage of the release.
Snide attempt? seems your a bit angry?
The question is, should "we" accept that we need update our firmwares on our Blu-Ray players or should we not. Until authoring is streamlined and every hidden secret of failure is known i think it will be a fact of life.
Um, guys, I didn't mean to kick off another religious war, I was just pointing out why a manufacturer wouldn't want to be a small player in the BD business. The simple fact is that authoring studios have limited resources, and they're going to expend those resources where they do the most good, by testing on the players considered to be the most popular.
There are always going to be compatibility problems with BD, the spec is just too loose (not to mention insanely complex), and there are just too many competing implementations. It could easily have been as bad with HD DVD, except for the fact that all our players had the same core code, pretty much. Which meant that the players themselves became the de-facto standard, and new players would have to match their performance, irrespective of what the spec said.
It'll get better for BD as the number of implementations slowly whittle down to the most popular and it becomes cheap enough for a new manufacturer to just license a known good implementation instead of rolling their own. I suspect that's already happening, but I also believe it would be difficult for the XBox to do that due to it not using one of the standard chipsets, so it would be plagued with the same compatibility issues you see the small players having now.
Just for an example, the eventing model in the HD DVD spec was essentially described in a single paragraph, with a reference to the W3C eventing spec - the problem is that the eventing spec has no concept of multiple applications, or default behavious, or levels above document root in the object tree. It took us a huge email thread, and a couple of us sitting down and defining _exactly_ how the events would propagate inside an app, and between apps, and how event capturing would behave before we had something that could actually _work_. A fair number of shipped discs use eventing between apps (essentially every Universal title), and even a slight implementation change in the eventing model would break all those discs.
I'm actually impressed by how _few_ problems the BD folks are having.