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.

Not a counterexample of the type system of Rust itself, but this one with LLVM following C and C++ definitions of "side-effects" is interesting: https://counterexamples.org/eventually-nothing.html

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

$250 is the same amount of money regardless of what the laptop cost or what you're doing with it.

Mostly by looking at the level of functionality and comparing to other software, cross referenced against my career as a programmer.

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.

Yeah, and you could argue that ARM and RISC-V Windows and Linux wouldn't be PCs, but I don't really see the value in using the terminology for such a dated use. It's not really useful anymore since none of the same software is compatible across different OSes anymore.

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

That's an insultingly uncharitable read, and is loaded with some pretty unfair assumptions.

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?

I'll gladly play Apple processor prices for an Apple processor, but I'm not going to pay Apple PC prices for an Apple PC when all I really want is the CPU.

They'll do free replacements if it's a known defect, and especially if it's widely experienced. Even Nintendo does that if they sniff a potential class action and want to avoid it.

Oh yeah, I remember they did a free out of warranty replacement on one of my MacBooks a bit back, but there was a potential battery explosion issue on that one.

Apple marketing made "Mac vs PC" to try to differentiate themselves, and I refuse to adopt their marketing terms as if they are facts. Most people who work with computers will call a Mac a Mac, but won't use the "PC" category as if it doesn't include Apple PCs.

Apple Silicon is really good for what it does. Apple does not create its RAM and the RAM is indeed equal for a significant markup.

Macs are PCs.

And looking at the Framework laptop shop right now, I see a 16GB DDR4 DIMM for $60, and you can throw in a standard M.2 storage module. Maybe Framework is just singularly better, but that's still a reason to not buy Apple for me.

How cheap is "pretty cheap"? They wanted $300 to replace the trackpad that suddenly stopped working on its own on my 2019 one.

Looking at the price estimator, battery service is like $250. That's not cheap.

It's hard to find a UI worse than that of your average Smart TV. They're in a league of their own when it comes to spectacularly terrible UIs.

I like having a real package manager, good native containerization and virtualization, being able to develop on the same OS that the deployment target is, and a large handful of things that are simply more pleasant on Linux (like the assumption of a case-sensitive filesystem, better job scheduling and daemon handling, more scriptable system utilities, and simply more transparency and control of my machine front to back). The DE situation is crappy, but I'd expect this place to recognize that there's more to an OS than the DE, and that developers might take a subpar DE for a better development experience as a whole.

It's the combination of OS and price. When Apple is very often double or more the price for competitive products, charges exorbitant prices for modest upgrades (currently $200 difference between 8 and 16 GB RAM. Over $400 for 1 TB SSD when a good 1TB M.2 goes for about $55), the OS is annoying and restrictive, and my choices for replacement OSes are all very experimental compared to non-Apple hardware, why would I spend significantly more for a significantly worse experience?

And I'm happy to pay for quality tools, but I'm not spending $20 for copy-paste (edit: hyperbole. Every time I find some missing simple functionality that is available for free and easy on Linux, the Apple equivalent is available on the app store for a significant charge. Some games are simply more expensive on iOS than elsewhere because the developers know Apple users will pay more). Apple is still largely in the "luxury designer product with a consumer base of 10% historical savvy users who prefer it and 90% rich kids who like the logo and don't mind flushing money down the drain for a brand".

They excel at a lot of workloads I do a lot of, and I'm really keen to experiment with non x86 desktop processors.

What are the affordable substitutes for the M2 Ultra?