Live data from Hacker News

Apple limits daisychaining of non-Apple displays in OS X

apple.stackexchange.com

51–59 of 59 posts

Re: Apple limits daisychaining of non-Apple displays in OS X

#51

Earlier quoted context omitted.

OS X generally has terrible 3D support and the same hardware on Windows will perform much better. That's unfortunate but no reason to go to court for. Apple writes their own device drivers and they write them to the extend their software and hardware needs it and no step further.

It seems to be intentional though. I seem to recall Microsoft and IBM got into big trouble for anti-competitive conduct. This is the sort of thing that brings about anti-trust suits.

It seems intentional in a "it would cost resources to extend this past what we benefit" way. In other words, a business made a cost-benefit analysis.

I fail to see where your frustration is coming from, or why it's targeted at Apple. It's most likely just a calculated cost savings measure.

Re: Apple limits daisychaining of non-Apple displays in OS X

#52

Earlier quoted context omitted.

It seems to be intentional though. I seem to recall Microsoft and IBM got into big trouble for anti-competitive conduct. This is the sort of thing that brings about anti-trust suits.

It seems intentional in a "it would cost resources to extend this past what we benefit" way. In other words, a business made a cost-benefit analysis. I fail to see where your frustration is coming from, or why it's targeted at Apple. It's most likely just a calculated cost savings measure.

The frustration is targeted at Apple, because someone there likely made this decision... The support was likely already written, and expressly removed, because Apple makes Thunderbolt monitors. Not to mention that Apple is known for it's wide profit margin, so any cost/benefit analysis is less meaningful in that regard.

I'm not sure where you think said frustration should be directed.

Re: Apple limits daisychaining of non-Apple displays in OS X

#53

Earlier quoted context omitted.

It seems intentional in a "it would cost resources to extend this past what we benefit" way. In other words, a business made a cost-benefit analysis. I fail to see where your frustration is coming from, or why it's targeted at Apple. It's most likely just a calculated cost savings measure.

The frustration is targeted at Apple, because someone there likely made this decision... The support was likely already written, and expressly removed, because Apple makes Thunderbolt monitors. Not to mention that Apple is known for it's wide profit margin, so any cost/benefit analysis is less meaningful in that regard. I'm not sure where you think said frustration should be directed.

Rather than speculating on what Apple did internally, I think the real question is whether Apple advertises DisplayPort 1.2 support, since this feature is part of the DP 1.2 spec. So far I can't find anything about this on their product pages. If that's the case it's basically users demanding features that were never put into the specs of a product.

Re: Apple limits daisychaining of non-Apple displays in OS X

#54

"This question has been asked before and already has an answer." This is the single MOST ANNOYING thing about stack exchange. WHERE was this question asked before? How about a link to the original question? Hello?

It irritates me when they flag the question as duplicate and not provide a link to the possible original and it's incredibly hard to find a similar question. It wud be just easier to link the original instead of all the traffic coming from google finding a dead end.

It's impossible to do that on SE sites - if you try to flag as a duplicate, the site requires you to chose the question you believe the one you are flagging to be a duplicate of. The ability to vote is disabled until you do, and the site then shows the link in a comment and eventually at the top of the post if it gets closed.

Re: Apple limits daisychaining of non-Apple displays in OS X

#55

"This question has been asked before and already has an answer." This is the single MOST ANNOYING thing about stack exchange. WHERE was this question asked before? How about a link to the original question? Hello?

Good news - it's literally right there at the top of the question. "This question already has an answer here:" with a link. It is impossible to close a question on SE sites as a duplicate without providing the question being duplicated, for this very reason.

Re: Apple limits daisychaining of non-Apple displays in OS X

#56

Earlier quoted context omitted.

I hate to say this, but the U2414H is a better monitor. Zero processing latency (not 1 frame, not half of a frame, but real world measured latency of less than 1 ms; virtually all of the gamer monitors out there are at least 1 frame and the only ones that get I have three on my desk.

It's 1920x1080, though, right? The U2515H is 2560x1440. That difference is far more important to me than a few milliseconds of latency (I don't play games).

Yes, but they're also often for sale for around $250. I bought three.

Re: Apple limits daisychaining of non-Apple displays in OS X

#57

Earlier quoted context omitted.

The frustration is targeted at Apple, because someone there likely made this decision... The support was likely already written, and expressly removed, because Apple makes Thunderbolt monitors. Not to mention that Apple is known for it's wide profit margin, so any cost/benefit analysis is less meaningful in that regard. I'm not sure where you think said frustration should be directed.

Rather than speculating on what Apple did internally, I think the real question is whether Apple advertises DisplayPort 1.2 support, since this feature is part of the DP 1.2 spec. So far I can't find anything about this on their product pages. If that's the case it's basically users demanding features that were never put into the specs of a product.

Then Apple is in trouble:

Mini DisplayPort Connector

The Mini DisplayPort Connector is a small form factor connector designed to fully support the VESA DisplayPort protocol. It is particularly useful on systems where space is at a premium, such as portable computers or to support multiple connectors on reduced height add-in cards.

https://developer.apple.com/softwarelicensing/agreements/min...

Re: Apple limits daisychaining of non-Apple displays in OS X

#58

Earlier quoted context omitted.

Rather than speculating on what Apple did internally, I think the real question is whether Apple advertises DisplayPort 1.2 support, since this feature is part of the DP 1.2 spec. So far I can't find anything about this on their product pages. If that's the case it's basically users demanding features that were never put into the specs of a product.

Then Apple is in trouble: Mini DisplayPort Connector The Mini DisplayPort Connector is a small form factor connector designed to fully support the VESA DisplayPort protocol. It is particularly useful on systems where space is at a premium, such as portable computers or to support multiple connectors on reduced height add-in cards. https://developer.apple.com/softwarelicensing/agreements/min...

It doesn't say which version though.

Re: Apple limits daisychaining of non-Apple displays in OS X

#59

Earlier quoted context omitted.

Then Apple is in trouble: Mini DisplayPort Connector The Mini DisplayPort Connector is a small form factor connector designed to fully support the VESA DisplayPort protocol. It is particularly useful on systems where space is at a premium, such as portable computers or to support multiple connectors on reduced height add-in cards. https://developer.apple.com/softwarelicensing/agreements/min...

It doesn't say which version though.

Mini DisplayPort started from 1.2 of the DisplayPort standard.
Post reply on HN