Linked by Eugenia Loli on Fri 24th Jul 2009 22:52 UTC
Thread beginning with comment 375230
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: iTunes is not...
by echo.ranger on Mon 27th Jul 2009 20:02
in reply to "RE[3]: iTunes is not..."
"Are you going to argue that Apple must, because now they have a huge portion of the downloadable music market, violate all their contracts, and also spend money to support their competitors at an equal level of functionality as their own devices
A lot of people have posted similar lines of reason on this thread - they are ALL bunk... No one, repeat NO ONE, is saying that Apple should support interoperability. The issue is that Apple is intentionally blocking interoperability. "
Maybe I'm missing something (or am just ignorant), but with the fact that Apple provides the iTunes library in xml format on the machine where its installed would seem to nullify that argument. Apple HAS provided the data from iTunes in a way that allows interoperability, they don't need to make iTunes directly support or interface with other devices. If Palm wrote their own sync app that utilized the xml data from iTunes this would be a non-issue as I understand it (but I probably don't since I don't follow Palm circles very closely since the original Palm left US Robotics' hands).
Please correct me if I'm wrong.




Member since:
2006-01-25
A lot of people have posted similar lines of reason on this thread - they are ALL bunk... No one, repeat NO ONE, is saying that Apple should support interoperability. The issue is that Apple is intentionally blocking interoperability.
A competitor has (legally) reverse engineered a method of interoperability, and Apple has changed their software in order to block that competitor. The change has no other purpose - it does not improve their product in any way. IF Apple is a monopoly - that is an abuse of monopoly position.
Again, just to stress the point - Apple is NOT required to provide that - what they are required to do is not abuse their monopoly power to block competition.
These are completely separate issues. Palm falsifying their vendor ID is clearly a violation of USB compliance - I don't think anyone is arguing that it isn't. But that issue is between Palm and the ISB-IF, not Apple - Apple has nothing to do with it.
Arguing that Apple's actions are "good" simply because you interpret Palm's actions as "bad" is silly. The two things are not even related.
That may be true. I would say it is a LONG stretch, but it is arguably possible that this could be considered a forgery case... But again that doesn't in any way redeem Apple's behavior - and Palm's argument will of course be that they would not have to "forge" anything if Apple had not blocked interoperability with their product.
And yet there is a THRIVING market for 3rd party parts for GM products. GM dealers will generally use on GM parts - which is their prerogative. But if you put a non-GM part into a GM product guess what - it has absolutely no effect on warranty coverage unless GM can demonstrate that the part contributed to the damage being repaired under warranty... Obviously the part itself is not warrantied by GM, but its use does NOT affect the warranty of the vehicle itself.
The same basic reasoning applies to Apple. Unless it can be demonstrated that Palm's device causes issues with iTunes Apple has no grounds to argue on.
Btw, Apple is perfectly within their rights to add a clause to their iTunes software license (if they dont already have one like this) stating that they offer no support for syncing with non-Apple hardware. To stress the point again, Apple is NOT required to support their competitors.
Not at all. That would arguably be considered a product improvement - nothing at all wrong with them doing that. At that point it would be Palm's responsibility to maintain interoperability if they so chose to - and Apple does not have to support their efforts in any way.
Making a change that is NOT a product improvement which has no other purpose than to block interoperability is the problem...