![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Nope, you can do that with GPay, which is not the same as Google Pay, which is not the same as Google Wallet, but they all connect to the same account. Yay Google naming 😑.
Nope, you can do that with GPay, which is not the same as Google Pay, which is not the same as Google Wallet, but they all connect to the same account. Yay Google naming 😑.
“Google Pay” app is going away, but the “GPay” app is not, and you can use that for person to person transactions. Yay Google naming conventions.
Because Google is Google and can’t keep their own shit straight, there is a bit of confusion. “Google Pay” is going away, but “GPay” is not. You can still use the GPay app for person to person transactions. Google Wallet is used for things like tap-to-pay. Both apps link to the same underlying account.
Also QA, issue tracking, and litigation protection. This includes worker protection.
“Those bolts? We have the record right here from the very wrench that tightened them that shows they were tightened to spec on that plane.”
I believe the issue isn’t one of laws, but enforcement. If a person is physically capable of modifying the code their cars runs and then operating it on a public road, then someone will, illegal or not. That is what puts the lives of others at risk. Hell, I can already imagine websites where you can download untested mods to apply to cars that people will apply with no knowledge of how it works.
That poses an interesting question. If they can change the terms, and say that you agree to the changes by continuing to use their software, and they remove the clause allowing you to use the previous agreement, then can you use the previous agreement? It’s a bit of a buried shovel problem. Have you agreed to not use a previous agreement by continuing to use the software, or can you stick to the old agreement that lets you use the old agreement?
“By continuing to use the software, you agree to the new terms…” which is, of course, hogwash, but wouldn’t stop them from say “Sorry, the new terms were released and you agreed, so pay up.”
Enforcability is one of the major issues, and why companies try so hard to keep issues like this from the courts.
But do the terms you signed say they are allowed to change the terms at any time with notice?
I’m not saying planned obsolescence isn’t a thing (because it is), but that’s not the only reason. Making phones smaller, lighter, faster, and more feature-dense all mean that the phone has to be built with tighter manufacturing and operating tolerances. Faster chips are more prone to heat and vibration damage. Higher power requirements means the battery has a larger charge/discharge cycle. And unfortunately, tighter operating tolerances mean that they can fall out of those tolerances much more easily.
They get dropped, shaken, exposed to large environmental temperature swings, charged in wonky ways, exposed to hand oils and other kinds of dirt, and a slew of other evils. Older phones that didn’t have such tight tolerances could handle all that better. Old Nokia phones weren’t built to be indestructible, they are just such simple phones that there isn’t much to break; but there’s a reason people don’t use them much anymore. You can still get simple feature phones, but the fact remains that they don’t sell well, so not many are made, and the ones that are made don’t have a lot of time and money invested in them.
Now Voyager is an extremely simple computer, made with technology that has huge tolerances, in an environment that is mostly consistent and known ahead of time so the design can deliberately account for it, had lots of testing, didn’t have to take mass production into its design consideration, didn’t have to make cost trade-offs, and has a dedicated engineering team to keep it going. It is still impressive that it has lasted this long, but that is more a testament to the incredible work that was and is being put into it than to the technology behind it.