Assuming you are not being disingenuous: there is a trade off with a lot of uncertainty - other things are also implicated in stomach cancer, and at the same time untreated dental disease causes other health problems too.
But I prefer to rely on brushing my own teeth and avoiding certain foods to maintain my own health, rather than have a medication added to my water supply because the guy next door does not take care of his health.
I've had longer delays in the UK. My car was damaged by another driver. I sent my dash cam recording to my insurer and then both insurers dithered for months until I threatened to get the government ombudsman involved.
There have been a few products like this announced recently and they all have intro level examples on the home page. Can yours deal with things like entity-attribute-value model tables?
You have no information on how I approached using chat gpt, what prompts I used, how close its replies came to being correct/useful or not, but you decided to regale us with an irrelevant car metaphor anyway.
I tried chat gpt for the first time today. I asked it to write me a script to fetch some data from an API. It didn't succeed, and this kind of common task from a well-documented API should (I thought) be a slam dunk.
Involuntary admission is not automatically inhumane, but you do need to be admitting people to well-run hospitals and have a system in place to protect everyone from malicious admission. Both of those things cost money.
I once hypothetically saved a few dozen colleagues from dying in a fire. All of these people had at least a degree and many were educated to PhD.
The fire alarm sounded and at the bottom of a stairwell the exit door would not release until someone operated the emergency release break-glass panel. But none of these educated people grasped that. Worse still, none of them thought to use a nearby heavy steel trolley as a battering ram. One guy is trying to phone for help, which was pointless as the alarm sound makes conversation impossible.
I'm one of the last down the stairs. I look at the people, the closed door, the steel trolley, and the emergency door release panel. Realising I'm not going to have the fun of trashing the doors, I operate the release panel and we all leave.
A lot of people have to work two jobs just to afford food and shelter. Granted there are also people trying to live a Champaign lifestyle on a lemonade budget, but how do you address the first group?
That's fair enough if your job is in front end or whatever and you just need to use a table or view that someone else built for you.
I comment I read somewhere was that SQL goes from basic to advanced with nothing in between. It's a slippery slope of course: you start writing your own query and then you figure a more sophisticated query would be helpful and pretty soon you're having to care about optimisation and indexes.
(But I concede that effort and productivity are not the same thing.)