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.

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.

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.

> 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.

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.

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.

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.

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.

Somehow, I constantly come across lifelong programmers who insist on working for free. They get software for free, give their software away for free, and very often have encompassing philosophies of software freedom (and often freedom of information and data in general). I find it very sad that the idea of mutual support and love of software and art without money changing hands is regularly met with such resistance from people who haven't experienced the joy of being in a community that doesn't constantly look to extract cash from their own.

I know what exploitation is, but it's not the group of programmers working for the good of one another.

"Mac vs PC" was way after Windows software was already not compatible with IBM PCs, so by that point, the implication was just "PC == x86", and Apple was already transitioning to Intel as well. "PC" being tied to a specific Intel processor is confusing. It's all very bizarre and mostly marketing.

I am a programmer, and I contribute plenty of FOSS code. Very often, I find a solution with some issues and submit PRs. I'm not arrogant enough to do a couple hours of work and charge $20 per download for it, and I'm not a useful enough idiot to work for free for Apple, so I guess that bars me from doing the same on MacOS (even though I have to work with it for work). I guess if some of my code is general enough, some well-meaning Apple FOSS users can port it over.

It's interesting to me how much comradery and work for the general community is done in the open for and among Linux and BSD users with only the expectation that others will do the same for them, but many Apple users I've run into are like you, treating the simple desire to make things better for people with absolute derision and disgust. I guess if you aren't maximizing profit, why do anything at all, right?