This is yet more corporate/government overreach on devices that you're supposed to own.
Trying to prevent software from being available/installed that isn't even in the "legitimate harm" list. That's insane.
I could rant a lot about where we're in a really horrible you don't own your phone and other people believe they own it world, but that would be going off topic here. (I.e. business you go to the store is trying to force and pressure you to install apps.. i.e. sams club, or tours/businesses pushing you excessively to use whatsapp, etc )
Just because the keys reside on someone else's device, that doesn't mean you aren't responsible for their money when you control the code that is running.
This move feels inevitable. I expect we'll come to see an all-time high in "vibe-coded" apps and services/products built with surface-level understanding by creators and used by people with even less technical awareness.
Most developers in this new wave don't fully grasp the systems they're building, and end-users operate in total opacity. I have personally used AI to generate code scaffolds, and spend hours debugging edge cases, printing GitHub issues, and feeding API docs back into the system to stair it right enough times that I end up understanding a lot more what it is I plan on implementing as I reach a solid implementation. The average user wouldn't even know where to start with that.
Google's policy isn't an overreach; more like a reaction to the coming tsunami of superficially functional but fundamentally fragile tools. This is just the first domino. Expect more platform-level interventions as poorly understood tech stacks meet real-world consequences.
The era of "move fast and break things" is colliding with domains where broken things ruin lives. I wouldn't want any family members/close friends getting to swallow the latter pill.
11 comments
[ 4.6 ms ] story [ 35.8 ms ] threadTrying to prevent software from being available/installed that isn't even in the "legitimate harm" list. That's insane.
I could rant a lot about where we're in a really horrible you don't own your phone and other people believe they own it world, but that would be going off topic here. (I.e. business you go to the store is trying to force and pressure you to install apps.. i.e. sams club, or tours/businesses pushing you excessively to use whatsapp, etc )
Most developers in this new wave don't fully grasp the systems they're building, and end-users operate in total opacity. I have personally used AI to generate code scaffolds, and spend hours debugging edge cases, printing GitHub issues, and feeding API docs back into the system to stair it right enough times that I end up understanding a lot more what it is I plan on implementing as I reach a solid implementation. The average user wouldn't even know where to start with that.
Google's policy isn't an overreach; more like a reaction to the coming tsunami of superficially functional but fundamentally fragile tools. This is just the first domino. Expect more platform-level interventions as poorly understood tech stacks meet real-world consequences.
The era of "move fast and break things" is colliding with domains where broken things ruin lives. I wouldn't want any family members/close friends getting to swallow the latter pill.
│
└── Dey well; Be well
https://x.com/newsfromgoogle/status/1955741506440192463?s=52...