Taywee

Specifically for weight control.

If you're already in the middle of the healthy BMI range and not having trouble keeping a healthy weight, I don't think there's been a demonstrated harm.

That's a ridiculous analogy. What about suger-free sodas, or sparkling water without even artificial sweeteners? What about people who drink soda, but still don't go over the daily recommended sugar intake, and otherwise have healthy lifestyles?

I'd be willing to make two assumptions:

1. A gaping wound in your leg is probably less healthy than a moderately-high sugar consumption.

2. People who are concerned about nanoplastic intake are probably also concerned about deleterious health effects of things like sugar intake.

Medical use of plactic is a minuscule minority of plastic use. The vast majority of disposable, single-use plastic is not actually necessary. I'd be shocked if less than 90% of single-use disposable plastic was from food containers. Hell, I'd be pretty surprised if it were less than 99%.

They do these kinds of studies on mice because mice have a high homology with humans, and a huge number of the findings extrapolate to humans.

Both of those things are straight-up improvements, even if they're not perfect. You can nit-pick every single thing all you want, but better is better.

"dearth" means "lack" or "scarcity". I think it's the opposite of what you meant.

Analgesic isn't a British word, though. It's used plenty in American medicine.

I just want reliable conversions. In my situation (duct taping a very old service to a newer one), I needed to read structured files with UTF-16 fields, and process them into an eventual UTF-8 file written to a different location. The host this needed to run on did not have any unicode locales installed (and incidentally, I hate changing locales for my software because it's a program-global switch to flip, and most of my program still wants to run in the user's locale).

I found it ridiculous that there was no way to just convert UTF-16 to UTF-8 without either reinventing that wheel, pulling in an external dependency, or changing global state and having the right system locales installed (as well as knowing the name of at least one of those locales, and guessing a language along with it), despite having the latest C and C++ compilers at my disposal.

It sort of did, but in a completely different place past the critique section:

> But, rather than using them and needing to praying to the heaven’s the internal Multibyte C Encoding is UTF-8 (like with the aforementioned wcrtomb -> mbrtoc8/16/32 style of conversions), we’ll just provide a direction conversion routine and cut out the wchar_t encoding/multibyte encoding middle man.

Not sure why it wasn't mentioned up top. When trying to convert between UTF-8 and UTF-16 without doing it myself or pulling in external dependencies, this was the most annoying thing that slapped me in the face. This is the problem that makes reliable charset conversions between specific encodings actually impossible using just the stdlib functions.

I don't think that's what the complaint is. The complaint is that "multibyte" is not necessarily UTF-8. You can't just blindly convert to multibyte assuming that it's UTF-8, because it might not be. You can't convert between two encodings by just going through "multibyte", because it might actually not support all characters you might need to support.

So it really is a deficiency in C. It's nearly useless to have a "multibyte" or "wide character" encoding when those can mean anything. Having conversion between UTF-8 and UTF-32 is useful. Having conversion between "implemetation and platform dependent 'multibyte'" and "implementation and platform dependent 'wide character'" strings is nearly useless.

It's not a link, it's the image name that you'd directly use from docker or podman. And yes, that's the same one.

One of the things I found so confusing about docker at first was how much information you could leave out of your image reference and docker would assume the rest. I'd prefer if it only assumed localhost, and never automatically assumed any remote registry. There's really no reason for docker.io to be special.

> It took them years to permit uploading of vp9/opus webms

Did they finally do that? I left permanently a couple years ago (after being there regularly since 2006) because the small "these kinds of threads are why I still hang around this place" threads got more and more infrequent and the regular users got more and more annoying and less fun. Most of the site just became a constant pool of angry racism, cynicism, and paranoia. I can handle seeing stupid racism, but the death of fun and the constant angry sarcasm just got old.

Anyway, I was constantly annoyed that I couldn't upload vp9 webms, and that apng was also not supported given how much better than gif it was. Webp would have been decent, too.

> I don't think there's a truly safe programming language.

This is correct, technically, but you can achieve really high assurances of safety. "safe" is not a binary, but a spectrum.

The rest of the comment is patently false. It's actually close to the opposite of reality. The stricter the type system, the smaller the risk of unexpected behavior. Very very smart people who "know how to manage memory" use C and introduce memory errors very often. It's actually only in small, ungeneralizable programs where weaker type systems don't matter.

Good. I can't believe the Google argument for removal, being in effect "it's only slightly better in every single way than all the other formats we support, and not enough people jumped though the hoops to manually opt into it, so we're removing it entirely."