The road to mitigating climate change and pollution will be filled with small inconveniences. In the grand scheme of things, is it really that big of a deal to spend a few cents on bags that are much more likely to end up properly disposed of to reduce the outsized amount of plastic bag litter and energy/oil spent on creating said bags?

One possible suggestion, is it possible for you to get a reusable collapsing basket to keep downstairs for carrying groceries?

I mean, we’ve seen already that AI companies are forced to be reactive when people exploit loopholes in their models or some unexpected behavior occurs. Not that they aren’t smart people, but these things are very hard to predict, and hard to fix once they go wrong.

Also, what do you mean by synthetic data? If it’s made by AI, that’s how collapse happens.

The problem with curated data is that you have to, well, curate it, and that’s hard to do at scale. No longer do we have a few decades’ worth of unpoisoned data to work with; the only way to guarantee training data isn’t from its own model is to make it yourself

A lot of pro-birth people argue “obviously things are different if the mother’s life is in danger”, but that ignores that there’s often nothing obvious or definite about the line between “safe” and dangerous. Doctors are erring on the side of caution to avoid potential lawsuits and even jail time, and this is the result. People bleeding out in parking lots, suffering irreversible damage to their body, and people dying.

I guess the question is, what happens to the kernel when all the people who learned on C are gone? The majority of even the brightest new devs aren’t going to cut their teeth on C, and will feel the same resistance to learning a new language when they think that there are diminishing returns to be had compared to what’s new and modern and, most importantly, familiar.

I honestly get the hostility, the fast pace of technology has left a lot of older devs being seen as undesirable because the don’t know the new stuff, even if their fundamental understanding of low level languages could be a huge asset. Their knowledge of C is vast and valuable, and they’re working on a project that thrives because of it. To have new people come to the project and say “Yeah, we could do this without having to worry about all that stuff” feels like throwing away a lot of the skill they’ve built. I’m not sure what the solution is, I really don’t think there are enough new C developers in the world to keep the project going strong into the future though. Maybe a fork is just the way to go; time will tell which is more sustainable.

Permissive licenses mean faster and more widespread adoption, it’s up to project maintainers if the tradeoff is worth it. Ideally a company would realize that an open source part of their project probably isn’t radically going to affect their revenue stream, but you don’t just have to convince devs, you have to convince the suits and lawyers, and they will tell you to just build your own rather than give up any precious IP.