mianas
Much like the container tabs extension, in terms of requiring an addon for certain functionality. Or, if mozilla doesn't do it themselves, a (horrifying though warning) third-party-extension with an external helper application to connect to the serial device, and a API polyfill injected into every page.
Predictable statistics screams RNG, to me. Especially if the code author knew it was an imperfect solution, and didn't know of one that wouldn't cause this crash. (I've done stuff like this before.) Also, for the client to crash the server, it'd need to give it some form of bad/confusing data, but for some reason this doesn't happen with fewer users.
I think that was my logic at the time of writing that comment, though I've thought of another few guesses while typing this out/reading your follow-up.
This saves me an absurd amount of planning/thinking as I can compare an equivalent cost number whenever I see a substitutable product somewhere. Also saves you from being fooled by your own assumptions, like when the unit cost of the largest cereal box is higher than a smaller one.
Even earlier, I got into the habit of typing the where clause before typing the from clause. Not much of a change, but it feels more fail-safe.
AFAIK, anything UUID-sized or bigger doesn't have this problem on Earth.
Like, imagine a collapsible rod about a kilometer long sticking off the end of a space probe, lined up so it hits the surface as close to perpendicular as possible, each segment made of appropriate material for its impact speed. (I think once you go past the speed of sound in a material, you can't transfer any more force)
With the far end of the rod, which impacts first and with the most force probably vaporizing/creating a crater on the surface (useful to align the rest of the rod), and later sections crumpling in on themselves predictably, like a highway crash barrier or car hood. With a certain max amount of Acceleration, Jerk, Snap, etc... that the probe can survive.
I would very much like someone to explain why decelerating a spacecraft like this is infeasible/inefficient so I can stop thinking about it. Failing that, I wish to devote the next few years of my life to jamming a massive spear into the moon.
Some Italian construction company underbid, and slightly later went bankrupt after finishing some of the work. They just about missed the contract milestones for payment too, and got nothing out of it. Then, the contract went to someone else who bid, with expected costs adjusted. Think there was an 8-ish month delay.
Would you consider electric showers an exception? They only heat whatever water you're using. I've lived in houses with no hot water in the taps for months, but could still take a hot shower whenever.
Anyone else think the smartest move for microsoft here is to leave it up, unless another copyright holder complains?
Not only has XP been sunset many times, many years ago, it might finally have all of its bugs picked clean and unofficial patches made to shore up any systems too embedded to move off XP still.
In general, if you want to encode info in your IDs, you can do that. Just make sure you want to do that, and that you don't run out of entropy.
I view random UUIDs as a silver-bullet type solution to assigning IDs, without overlap. (8 bytes should be enough to just assign them at random)
For example, they have a (heavily limited) de-facto warrant canary. Since damn near all of them specify that no data should be deleted for a period of time, posting is disabled on a board, or the entire site so nothing gets deleted.
They also disallow posting of files with embedded data (based on some heuristic) and either strip exif data, or forbid posting images containing it. (the exif stripping thing comes from people accidentally doxing themselves by posting an image from facebook a few years back)