News for hackers. Stuff that matters.
Re:Warning: 2016 MacBook Pro is not compatible with Linux by teto-plz on Thursday November 10, 2016 @06:07PM (#12925452)
Two things being compatible with each other is a symmetric relation, so the order doesn't matter.
Re:Warning: 2016 MacBook Pro is not compatible with Linux by gnicholas on Thursday November 10, 2016 @06:18PM (#12925578)
When previous devices in a series were compatible, things are a little different.

When I upgraded my iPhone to iOS 8 (in 2014), it stopped connecting via bluetooth with my car (2011 Subaru, FWIW). Apple told me it was a Subaru problem. I reiterated that the problem was caused by my upgrading iOS, and that nothing changed in my car. They said to get a firmware upgrade for my car.

So incompatibility can be symmetric, but for people with an expectation based on prior compatibility, the party that whose update triggers the issue will be seen (fairly or not) as the cause.

Re:Warning: 2016 MacBook Pro is not compatible with Linux by coldtea on Thursday November 10, 2016 @10:06PM (#12927235)
When describing abstract entities maybe, in real life, order always matters.

E.g. if you sell an office suite and it doesn't support DOC and XLS files, it's your fault and users will call you for it. It's not Microsoft's job to go make sure Word and Excel work with your office suite.

Re:Warning: 2016 MacBook Pro is not compatible with Linux by evincarofautumn on Thursday November 10, 2016 @08:05PM (#12926432)
True, but we usually phrase it in terms of the new thing’s compatibility with the old. In this case, Apple chose not to make their laptop compatible with the existing Linux. Nor, I think, should they necessarily have been expected to—it’s proprietary hardware, meant to run their proprietary OS.
Re:Warning: 2016 MacBook Pro is not compatible with Linux by lanna on Thursday November 10, 2016 @10:07PM (#12927237)
no, it's not
Re:Warning: 2016 MacBook Pro is not compatible with Linux by pinkrooftop on Friday November 11, 2016 @09:28AM (#12930859)
logically yes, but the subtext of this usage in English adds hidden variables