I got one post (not comment) over 600 and I felt like I was elected mayor or something
PeriodicallyPedantic
I think you make some very good points.
It's also important to remember that "perfect" is the enemy of "good". There will never be a perfect ally, because allies don't have the same lived experience. But (I think) that allyship is still a good thing.
I still never got a clear answer on who shot the firefighter, he didn't seem close to the podium
I'm glad I clicked on that
Thank you, that helped a lot!
I'm still a bit confused about what it means to modernize an old joke, in this context, but I think I more or less got the picture
I'm unlikely to listen to the whole album. To be honest I'm unlikely to listen to any of it.
With that in mind, care to explain this joke that clearly wasn't aimed at me?
Ah, a day well spent
Not only the pollution.
It has triggered an economic race to the bottom for any industry that can incorporate it. Employers will be forced to replace more workers with AI to keep prices competitive. And that is a lot of industries, especially if AI continues its growth.
The result is a lot of unemployment, which means an economic slowdown due to a lack of discretionary spending, which is a feedback loop.
There are only 3 outcomes I can imagine:
- AI fizzles out. It can't maintain its advancement enough to impress execs.
- An unimaginable wealth disparity and probably a return to something like feudalism.
- social revolution where AI is taken out of the hands of owners and placed into the hands of workers. Would require changes that we'd consider radically socialist now, like UBI and strong af social safety nets.
The second seems more likely than the third, and I consider that more or less a destruction of humanity
I wasn't taking about new fields. I was talking about resource partial updates (eg PATCH, or commonly the U in CRUD).
If you just want to update a single field on a resource with 100 fields, rather than GETting the entire resource, updating the single field, and PUTting whole thing back, just do a PATCH with the single field.
Likewise if you're POSTing a resource that has nullable fields, but the default value isn't null, how do you indicate that you want the default value for a given field? Do you have to first query some metadata API? That doesn't seem ideal, when this existing pattern exists
And the highest level of disappointment is finding a 10 year old stack overflow post that is exactly the problem you're having, but then discover that not only does it not have an answer but you're the one who asked it π