291–300 of 354 posts
Earlier quoted context omitted.
If I'm not mistaken, WINE is now capable of running 32-bit Windows binaries on 64-bit-only macOS as well, so that may also be an option particularly for more simple apps.
I don't think Wine can, but Crossover definitely can.
Earlier quoted context omitted.
The first except for Blackberry. Before IOS or Android even existed Blackberry had granular per app permissions. I don't disagree with your argument though, of the modern mobile OSs Apple moved to towards the per-app model before everyone else. I just find it interesting when Apple or Android gets coverage/credit for a feature that has long existed but was forgotten or ignored.
The problem is BB wasn't around by the time smartphones became more than a niche product. The list of prior work that influenced Apple, or any tech company, is usually far too long to list.
Agreed, but that doesn't mean we should default to "Apple was the first" simply because we can't wrap our heads around the pre-iPhone days.
Earlier quoted context omitted.
My other major contention is that Display Stream Compression has been broken since .0 betas through .1. I have 2 27" 4K HDR 144Hz monitors. On Catalina I can drive them at full spec on my 2019 Mac Pro, with a W5700X. On Big Sur, my options are HDR @ 60Hz, or SDR @ 95Hz. Not to mention the monitors also got a firmware update to unlock 165Hz, which neither Catalina or Big Sur recognize.
Which monitors are you using?
I have heard about the issue on a few other forums with other monitors. The only one I haven't heard about in either direction is the ProDisplay XDR.
Earlier quoted context omitted.
Having worked at Apple and other big companies it's almost always Engineers and PMs making these decisions. It's not like Tim Cook or Craig Federighi is running around demanding people add Apple apps to a firewall exclusion list. They have much bigger things to worry about. It's just that as an engineer you are often in a bubble and can't foresee every implication of your decision. That's why Apple has the Developer…
> Having worked at Apple and other big companies it's almost always Engineers and PMs making these decisions. I wonder what the backstory to the original decision was. Pure speculation: a "bug" was reported in which something was broken, and it turned out to be because a third party firewall was blocking access to some Apple-hosted service, and someone started working on "how to fix the bug", and the "bugfix" was to…
Earlier quoted context omitted.
Some people find it psychologically easier to sit in the shit when they discover they are not alone. Some even go further and trying to justify the shit when there is a lot of it. I am not one of them, so for me shit is still shit and I prefer to see it for what it is. Besides, can two wrongs make something right ?
I am not suggesting it is perfect, but that it may be a little hyperbolic to say any os you load on a Mac is not it's 'own OS' because it relies on closed bootloaders/firmware. If that is the case, then what does every other computer run? Is Linus's own operating system not his own because he loads it on an Intel or AMD processor?
I am glad that the public backlash forced them to fix a deliberate BACKDOOR that they had introduced (by design) in the Network Extension Framework that macOS Big Sur now forces all the firewalls to use. (At least, they claim to have removed it). But it is hard to trust them again, and I would prefer to use a firewall that uses its own kernel extension to manage the network than using Apple's API again. (Obviously th…
Earlier quoted context omitted.
It’s inaccurate to say “Apple selling user data to US government”. That’s not what the article claims (the word “sell” doesn’t even appear in the text), and there are in fact many consumer data brokers who really do sell data to law enforcement.
I don't think it's inaccurate; the IC pays the data providers (presumably for implementation/overhead) for receiving the FAA702 (PRISM/FISA) data. Which data is picked by the US government, and no warrant is required. Apple provided data on 30,000+ users to the US government without a warrant in 2019, per their own transparency report. If they received money for the program, they are indeed "selling user data to [the…
Earlier quoted context omitted.
I don't think I'd call it a bug. It's a poor decision. I can easily believe that it wasn't a decision made with malicious intent; the culture at Apple seems (at least from the outside, judging by results) to encourage an "it's okay to give our own software special exceptions" mentality.
You could call it an entitled opinion.
This firewall issue isn't the only privacy feature strip from Big Sur release. Unfortunately no big media care about other huge problem Apple introduced. My only hope they will also fix full disk encryption in this update. Since Big Sur broken installation of macOS on passphrase-encrypted disk partitions. I bought into M1 hype and now it's end up that you no longer able to have separate password for the disk encrypti…
In Case You Didn't Know: Big Sur on M1 (and possibly on Intel) maintains a persistent, hardware-serial-number linked TLS connection to Apple (for APNS, just like on iOS) at all times when you are logged in, even if you don't use iCloud, App Store, iMessage, or FaceTime, and have all analytics turned off. There's no UI to disable this. This means that Apple has the coarse location track log (due to GeoIP of the client…