I haven't tried on macos, but yeah, the biggest problem right now seems to be implementation differences with how embedded spaces are handled. Earlier, the biggest cross-browser issues were pixel alignments within the QR codes, but those seem largely resolved.
Fair warning though: this was designed and implemented by an LLM, as an experiment to see if it was possible. I only guided it to a working solution by pointing out problems, and never dug deeply into its inner workings.
It is not a tricky problem because it has a simple and obvious solution: do not filter or block usage just because the input includes a word like "gun".
My dad wears smart glasses because he's nearly deaf and the classes show captions for the person he's talking to. They're great. He doesn't use or care at all about the camera. Having the captions would be very useful to him in a courtroom setting. Collateral damage I guess.
It's not enclosed in the final product. It is used during manufacturing. For example, you mechanically compress helium to get liquid helium, then when it depressurizes back to ambient pressure, it's -269 C, which is pretty close to "as cold as possible", and colder than any alternatives.
> > some folks want to use lossless cut
> In that case I would encourage you to ruminate on what the following in the post you're replying to means and what the implications are:
You may have misunderstood the comment: "lossless cut" is the name of an ffmpeg GUI front end. They're not discussing which exact command line gives lossless results.
I was curious what the protein picture was showing:
"Figure 1 Example predictions of SimpleFold on targets ... with ground truth shown in light aqua and prediction in deep teal."
and now I'm even more curious why they thought "light aqua" vs "deep teal" would be a good choice
I don't know (and don't need you to elaborate on) exactly what you're referring to in that last sentence, but I suspect you are confusing Eric W. Weisstein with Eric Weisstein.
Lazy, or more efficient? If you type a time and hit start, you're not microwaving until you're done with all the buttons. If you hit "QS" a bunch to reach the duration instead, the microwave starts cooking immediately on the first press. Your nuggets get done a whole second earlier!
Relative to the handedness, one bolt is always moving with it, one bolt is always moving against it. Switching direction doesn't change that. So switching direction can't change whether it moves inward or outward.
Switching the direction that you're twiddling the bolts would have to change the direction of any movement. But by symmetry, clockwise and counterclockwise twiddling are identical (looking down on the head of each bolt, one is always moving clockwise and one is always moving counterclockwise). So there must be no in/out movement at all.
some math because I'm curious:
If you draw down and replace 50% of the water every day, each molecule has a 1/2 chance of sticking around.
After 3 months that's 1/(2^90).
A 5 gallon pot contains around 2^87 water molecules.
So after 3 months there's basically none of the original liquid left.
The Xbox came out when the PS2 did. When it came time for the next generation, Sony went with the obvious PS3. Microsoft of course couldn't compete with an "Xbox 2" vs a "PS3", and they couldn't skip right to "Xbox 3", so they called it the "Xbox 360", which was frankly genius because it had the 3 there anyway and put it on the same level in consumers' eyes.
But after that it all fell apart -- they had no good options. They still couldn't jump to "Xbox 4". Maybe "720" would have worked. Someone decided to have a clean break and restart at "One" but of course that fell apart immediately at "Two". So another clean break to "Series..". And by that point it's so screwy they've lost any chance of fixing it...