Right now another consumer electronics company could: a) produce a new unit with a high quality software, b) sell it at a competitive price point to Apple, c) create a product very similar to the iPod itself, d) there already exist many other competitors. Now on to whether it is a monopoly or not. It would need to be shown that Apple has conspired in some way to grow and maintain their market position in a way to be detrimental to consumers and other producers. Where innocent monopolies, as you may argue but I disagree, are what Apple has in the music player space. The courts have made a distinction between an innocent and a coercive monopoly. We'd have to wade through a lot of case-law here, but if you'll permit me the ability to speak without excessive sourcing (most of this can be found supported and sourced on Wiki). It may vary from nation to nation, but under US law the relevant act here is the Sherman Antitrust Act, which deals with single-firm anti-competitive behavior.
#Quicktime for chrome mac code
Quicktime is probably the one big chunk of code in OSX that still dates from pre-OSX days and hasn't been re-implemented in terms of something more modern like Core Foundation. The basic Quicktime architecture still deals with FSSpecs, memory handles, the old Component Manager, and API artifacts relating to the old code fragment manager from the pre-OSX days. In particular, programming codec plug-ins is horrible. it behaves a lot better on OSX if you're an end-user, but programming for Quicktime is a pain. If Windows users are tired of Quicktime, well. It's not 100% clear to me what the relationship between the two on OSX will be, but I'm guessing that Apple has given up on modernizing Quicktime and is just replacing it with AVFoundation. OSX 10.7 includes an OSX version of AVFoundation. iOS did away with this altogether and instead uses something called AVFoundation.
ha.Īctually, it's quite possible that much of what we think of as Quicktime will go away in OSX 10.7.Īpple has tried modernizing Quicktime with something called QTKit/Quicktime X. Odds of Google and Apple working together on Quicktime.
I'm not buying a Mac for home because Apple can't be trusted around VisualStudio.įlash gets the pass because Adobe lets Google worry about making sure updates are available on day 1.
#Quicktime for chrome mac update
Of course my dream is never to have to touch QuickTime or that horrid Apple Update garbage on Windows ever again. This change makes my web browsing experience SAFER and less frustrating. All are annoying, buggy, laggy and crashy.īoth Quicktime and Java were manually disabled globally on every browser I use and now I can feel safe leaving them on.
I strongly prefer that Chrome asked my permission before executing either the Quicktime or Java plugins just like it prompts for popups. Weither it's the crashing, slow startup times, bazaar buffering behavior or taking over way too many MIME types I hate it. And to be honest I'd prefer the Mac version not pull it in automatically either.
#Quicktime for chrome mac how to
It is a prime example of how to make a user experience complete shit. The Quicktime plugin on Windows is HORRID.
As someone who uses Chrome under Mac, Windows and Linux I applaud this move.
0 kommentar(er)
