(1) Practical. Many people look at git repos. No one audits with crxcavator.
(2) Traceability. git has secure hashes, and things can't change when you're not looking.
My experience is that Google cares deeply about its own security, but not much about the security of its users. This sort of change is reasonable, but completely outside of Google's psyche. Google will
(1) Silently disable Android updates, leaving many running exploitable phones
(2) Hold back security tools for Google Apps without a premium subscription. If your account was compromised, you have no way to do audits to understand what happened without $$$, which leads to many more attackers.
(3) Expires Chromebooks rather quickly. Fortunately, unlike Android, it lets users know, but given the target market, many can't afford to upgrade.
(4) Runs appstores full of malware. When malware is discovered, users have no way to know what it did. They're just notified malware existed.
(5) Doesn't allow any sort of reasonable sandboxing of Android apps. If an app asks for filesystem, maps, and other permissions, you need to agree to run the app. I can't have Android give a dummy location or otherwise
Given that the bulk of Google's business model is built on mass surveillance for advertising, with users-as-statistics, this isn't too surprising, but it's something to be aware of if you use Google.
I firmly believe in civil liability for software companies which ship insecure products. They shouldn't be able to externalize costs like this. Follow good security practices, or your insurance premiums go up.
... I'm not so sure about that. I suspect you might have liked the way the speaker changed the sound, but you could have gotten the same effect (with greater control) with the headphones and digital preprocessing.
The headphones will give a more faithful reproduction of the original recording.
Making a nearly-perfect class D amp isn't hard (which is not to say a lot of people haven't messed it up; there are a lot of pretty bad amps out there).
The hard part is the speaker itself. The mechanicals of moving a lot of air accurately are hard. You need a physically large woofer which moves over a long distance. If you do that, your woofer and tweater won't be in the same place, so your phase response will be wonky. You don't want the air cavity acting as a spring overpowering your driver, so you need a large box. Etc. By the end of it, it's super-complex. Headphones are super-easy in comparison.
At any sane price point, headphones blow away speakers.
It's hard and expensive to move a lot of air precisely, and speakers are influenced by room acoustics. $5 headphones beat $50 speakers. $80 headphones beat $200 speakers. And $200 headphones beat $400 speakers.
I can't afford to find out beyond that, but I suspect things get more nuanced on the ultra-high-end.
For me, for music, I'm happy with something like a Sony MDRV6 studio monitor, which sells for under $100. I don't know of speakers I like under $200.
Headphones are also nice for teleconferencing, where speakers aren't.
(2) Traceability. git has secure hashes, and things can't change when you're not looking.
My experience is that Google cares deeply about its own security, but not much about the security of its users. This sort of change is reasonable, but completely outside of Google's psyche. Google will
(1) Silently disable Android updates, leaving many running exploitable phones
(2) Hold back security tools for Google Apps without a premium subscription. If your account was compromised, you have no way to do audits to understand what happened without $$$, which leads to many more attackers.
(3) Expires Chromebooks rather quickly. Fortunately, unlike Android, it lets users know, but given the target market, many can't afford to upgrade.
(4) Runs appstores full of malware. When malware is discovered, users have no way to know what it did. They're just notified malware existed.
(5) Doesn't allow any sort of reasonable sandboxing of Android apps. If an app asks for filesystem, maps, and other permissions, you need to agree to run the app. I can't have Android give a dummy location or otherwise
Given that the bulk of Google's business model is built on mass surveillance for advertising, with users-as-statistics, this isn't too surprising, but it's something to be aware of if you use Google.
I firmly believe in civil liability for software companies which ship insecure products. They shouldn't be able to externalize costs like this. Follow good security practices, or your insurance premiums go up.