micampe

Steve Jobs was not at Apple between 1985 and 1997.

Also, the events described in your link all took place while Jobs was not at Apple.

The file format is still an ISO standard and pretty much anything reads it. Even Apple itself doesn't use the Quicktime container anymore (and hasn't for years). I didn't insinuate anything regarding open source, which doesn't appear anywhere in the part I quoted.

Edit: Oh, I noticed you significantly modified your first comment, that's why you now talk about open source when I never did. When I responded your comment read: “From the guy that tried to force QuickTime on us?”.

If you have Safari its Reader View works. Unfortunately none of the “readability”-type bookmarklets I know of work in this case.

I'm not the one considering one single outcome, if anything I feel like I'm the only one in these comments considering a different possible side effect of the trick.

Because you may prevent me from taking that seat without actually needing it. Sure you can but it's not nice to me.

I know I would be pissed if I needed to take a flight but it was fully booked, and then found out that a dozen people already planned to not show up.

I see this trick as not very respectful to other people.

This article has some more good tips on extracting information from those registers. http://www.sealiesoftware.com/blog/archive/2008/09/22/objc_e...

Note that some glyphs (g, l, i) can be customized and may look different from the screenshot in the default download.

I think that's an interesting question. Is a browser defined by its rendering engine or by its features and UI?

When Chrome used WebKit, it was clearly understood by everyone to be different from Safari, even though the rendering engine was the same (I know, the differences were big), but a Firefox browser that uses WebKit seems to not be considered Firefox.

Personally, while I understand the philosophical and political differences, I think the browser is defined by its features, not the rendering engine: the user wants their bookmarks to sync between the phone and the computer, they don't care whether the two programs use the same library to draw the page on the screen or not, just like they don't care which malloc() implementation they use.

To put it in fewer words: Chrome on iOS is still Chrome, not Safari, because it has Chrome's features.

(This would not have been true a decade ago, but rendering engines compatibility is much less of an issue now)

(That “currently” is just a weasel word, but this being the Internet I understand why you put it there)