My biggest issues with homebrew were dealing with versions of dependencies. If major updates for a package came out and you ran a `brew upgrade` (or a new member joins the team and installs it for the first time), it often wasn't trivial to switch back to the old version. Or if two projects have conflicting dependencies, for example one project was updated for imagemagick 7 but another still needed 6, that was an absolute nightmare to manage when using homebrew.
With nix, each project can define its own dependencies that have no impact on other projects. Combined with direnv, all you need is to `cd` into your project and you have the all of the dependencies at the right versions in your PATH.
Additionally, while definitely more complicated, nix (with nix-darwin and home-manager) can do way more than homebrew does. You can declaratively define pretty much the entire configuration for your machine.
I got a new Mac last week and with just a `git clone` and a few commands I had all my CLI tools installed, dotfiles setup, desktop apps installed, and even all of my macOS system settings configured.
If it does manage to do a good job imitating what an actual iPhone would do though - is there any way Apple even could shut it down without breaking iMessage on old iPhones or forcing people to update?
Then why isn't that happening on Android with Google Pay? Banks are able to handle NFC payments through their own apps if they want, but the vast majority support Google Pay and don't force users into their own app.
I suspect that is largely due to the success of Apple Pay. Banks used to have their own apps on Android for years and only grudgingly started to support Apple Pay since they couldn't use their own apps. They only started migrating from their own apps to Google Wallet/Pay after Apple Pay became a success and Android users started to feel left out. They would never have supported Apple Pay if they hadn't been forced to do so. In fact, even though there was no alternative they kept dragging their feet and complaining about it for years.
I have an Android phone and have every single one of my credit and debit cards from 7 different banks in Google Pay. Don't need to use the bank app for any of them.
EDIT: to be clear, currently on Android any app can handle NFC payments, not just Google Pay. Banks could easily force people to user their apps, but that's not happening.
Counterpoint: here in Israel we had (only) the bank apps on Android for 2+ years, and they were a combination of "okay" and "awful". My bank's app required to unlock your phone (with biometric auth), an app-specific pin code, and had a 30-second window. It then didn't work 30% of the time and required turning NFC off and on again to work. It took them over a year to change to "just unlock your phone".
Then Apple Pay launched here, contactless adoption on iOS became triple of Android's (despite Android having more than double the phones), and a few months later Google Pay launched in response with their better implementation. I'm guessing it was a combined "in response to Apple" from Google and "maybe this will increase adoption" from banks.
A possible consequence of the current legislation is that instead of a system-wide service where Apple Pay or Google Pay can work with different banks, each bank now demands to handle NFC payments within its own app. You may find that Google Pay is no longer supported by banks.
Sorry if it wasn't clear, that was actually my point - on Android even though banks have the ability to handle NFC payments within their own apps, the vast majority still support Google Pay and don't force you to use their app.
Most banks I know of only started supporting Google Pay after they deployed Apple Pay. Basically, Apple Pay showed consumers how good the UX can be which more or less forced the banks to Google Pay support so they can also have a good UX on Android. Without Apple forcing the use of Apple Pay I doubt it would ever have taken off.
NFC payments were possible through the banking apps on Android for years before Apple Pay launched in my country. Note that contactless payment had also been around here for years and pretty much all payment terminals supported it. Technically, everything was in place for it to be adopted, yet no one used it. Only after introduction of Apple Pay did it take off. Google Pay support followed the success of Apple Pay.
People have been talking about other companies doing that for ages, and many specifically choose Apple products because of their perceived commitment to privacy.
Apple's claims on how it will work are also completely unverifiable. What's stopping a government from providing Apple with hashes of any other sort of content they dislike?
And then Apple reviews the account and sees that what was flagged was not CSAM. And again, the hashes aren’t of arbitrary subject matter, they’re of specific images. Using that to police subject matter would be ludicrous.
How would Apple know what the content was that was flagged if all they are provided with is a list of hashes? I completely agree it's ludicrous, but there are plenty of countries that want that exact functionality.
If they have the hash/derivative they dont need to look on device or even decrypt, theyll know that data with this hash is on device, and presumably 100s of other matching hashes from the same device
The matched image’s decrypted security voucher includes a “visual derivative.” I’m sure in other words they can do some level of human comparison to verify that it is or is not a valid match.
https://www.androidauthority.com/chrome-os-on-android-proof-...