3 ms·
Is it Apple’s responsibility to maintain X on the Mac, though? If they want to implement something that may interfere with X (usually they do this kind of thin
by ChrisMarshallNY 5y ago
Is it Apple’s responsibility to maintain X on the Mac, though?
If they want to implement something that may interfere with X (usually they do this kind of thing because security), should they cripple the experience for half a billion users, to appease a small minority of techies?
I’ve been writing software for Apple devices since 1986, which means that I’ve had lots of rugs pulled out from under me, and have been incandescent with rage at Apple, many times.
That said, I’ve never regretted choosing it as my preferred platform, despite thirty years of insults and put-downs from other tech folks.
- DaiPlusPlus 5y ago> Is it Apple’s responsibility to maintain X on the Mac, though? Yes and no. So POSIX and the Unix Specification(TM) are standards thanks to the US federal government putting their foot-down and mandating that major contractors (like IBM, Sun, HP, etc) stop being incompatible with each other - and in-practice this also means having to support X. When OS X launched Apple loved to tell everyone that it was a true Unix(TM) system - (after-all, they did spend the money to get it certified as a real Unix system), and this meant that OS X-based systems were suddenly candidates for major US and international scientific and research contracts and gigs - which dovtailed nicely with the hype around their boasts of the PowerMac G5's literal supercomputer performance (and indeed: literal supercomputers comprised of racks of G5 machines in a bunch of US Navy Labs). Now, in the 2020s, it's clear that since the iPhone dominated their revenue that Apple is no-longer really interested in being part of government supercomputing and scientific computing contracts - the positive PR and technical credibility they gain from all of those government projects is insignificant compared to the cash revenue value of simply running another iPhone ad-campaign. The 2013 Mac Pro was solid proof that Apple does not value the high-end desktop and workstation computing markets anymore. Apple seems content to even let Windows take away their previously impentrable hold on the desktop video-editing market: whoever was using FCP on a MP in 2006 is almost certainly using Adobe Premier on Windows today. ...having said all of that, I was surprised to see that macOS 12.0 Monterey is still an official Unix(TM) certified product: https://www.opengroup.org/openbrand/register/brand3673.htm https://www.opengroup.org/openbrand/register/brand3673.htm - despite Apple's deprecation (and obsolescence?) of their support for X. ------------- So my point, if anything, is that if Apple wants to maintain its credibility as a high-end computing systems provider, it needs to revert back to doing far more than paying lip-service to being a Unix vendor - and that includes bringing native support for X (and some form of compatibility with the rest of the Unix/Linux GUI ecosystem) back into macOS - but if Apple continues to remain uninterested in selling themselves as a professional workstation vendor (which I feel is implicit in how they've been locking-down macOS and their Apple Silicon-based machines) then you're right, they don't have any responsibility to maintain compatibility with X. As it is, I don't know what Apple wants - or even what Apple would do in the event they lose their cash-cow and grip on the world when the iPhone is somehow obsoleted by a competitor. Of course if that happens then they'll quickly reverse-course and try to make-up for all of their substandard devX moments. ------------- > That said, I’ve never regretted choosing it as my preferred platform, despite thirty years of insults and put-downs from other tech folks. Pardon my asking, but I'm especially curious - what kind of software do you write? Unless you work for major creative-tools companies like Adobe - or a boutique Mac shop like Panic nor indie Mac App Store dev - I have trouble imagining what market there is for other types of software on the Mac. Whatever native macOS / Cocoa line-of-business software there was over the past couple of decades will have certainly transitions over to being a SaaS web-app by now.
- ChrisMarshallNY 5y agoOh, I won’t get into it. That’s a rabbithole that is best left to pocketwatch-bearing wildlife. Suffice it to say that a few folks (and I don’t claim to have a huge fanbase) seem to like the stuff I write. As fas as SaaS… Well, let’s just say that this is a familiar tune. That ol’ “thin client” zombie just keeps lurching out of the grave…
- dmitriid 5y ago> So POSIX and the Unix Specification(TM) are standards No one fully supports POSIX. Aside from server systems like AIX or HP-UX Apple is literally the only company that has a POSIX-certified consumer OS (OS X since 10.5 Leopard [1]). > So my point, if anything, is that if Apple wants to maintain its credibility as a high-end computing systems provider, it needs to revert back to doing far more than paying lip-service to being a Unix vendor - and that includes bringing native support for X What's "high-end computing systems provider"? Apple is doing really fine as is. Why should they do "far more", and why does this "far more" specifically includes support for X? They supported X for years (OS X 10.2 to 10.7), and then decided it wasn't worth it (and it isn't). [1] https://www.opengroup.org/openbrand/register/index2.html https://www.opengroup.org/openbrand/register/index2.html