Almost certainly. GPS is not only easily jammed, but easily spoofed. If the car believed GPS instead of its own eyes, so to speak, then there’s significant potential that you’d see glitches more often. It could also be something of a safety risk when using its self-driving capabilities.
Makes me wonder why there isn't a UI feature within easy reach to let the user drag a pin on a map and tap "I know I'm here right now"... and if that agrees with where GPS also indicates, let's it reset its notion of "I must be getting spoofed right now" thoughts in addition to calibrating other notions of current location.
Computers have been making decisions for a while now. As a specific personal example from 2008, I found out that my lender would make home loan offers based on an inscrutable (to me and the banker I was speaking to) heuristic. If the loan was denied by the heuristic, then a human could review the decision, but had strict criteria that they would have to follow. Basically, a computer could “exercise judgement” a make offers that a human could not.
Energy is how much work you can do. Power is how fast you can do it. When you express these in terms of densities, it’s how much energy a certain quantity of material can store, and how quickly that energy can be released from a certain quantity of material.
If you short out a AA battery, it will get warm for a little while. If you short out a 14500 Li-ion battery (which is the same size and comparable energy density), you might get a small explosion as it dumps its energy very quickly.
What’s your use case for locking dependencies on a single script?
One things that’s useful to my organization is that we can then proceed to scan the lockfile’s declared dependencies with, e.g., `trivy fs uv.lock` to make sure we’re not running code with known CVEs.
Just better visibility into the dependencies that come with the script (exactly for things like vulnerability scanning that you mention). It's also easier for reproducibility in someone else's environment when I can give them the exact list of dependencies instead of having them resolve it themselves using the inline declarations. Explicit is better than implicit :-)
I suspect there is a legal difference between offering a feature in the style of Quake (and calling it out as such) vs. baking it into your App’s branding.
It could potentially help with discoverability. As it stands, I’d imagine it takes a very particular sort of search query (either “open source fitness” in Google or “fitness” on GitHub) to have a chance at finding this. Unless your target audience is only the intersection of FOSS-advocates and fitness folks, you might be limiting adoption.
With that said, the website works just fine on my phone.
