It is one page of text. I think you can manage to read it and come to your own conclusions without relying on clickbait headlines and out of context quotes. https://www.nytimes.com/2026/04/23/technology/meta-layoffs.h...
replyNope. Sorry. Negative. Paywall.
replyYou clearly have an opinion you want to share, otherwise you wouldn't have written anything. Instead of just outright saying what you think, you are being vague. Why? It's true that Meta laid off a lot of people, and blamed refocusing on AI as the reason, but I still don't see how that somehow contradicts GP's quote above.
replyone time about 9 years ago I was in the comments of a stackoverflow question, and saying something like "an accessor function need not directly give the underlying structure of the data it's accessing, for example, just because in common lisp, (car nil) is nil and (cdr nil) is also nil, does not mean that nil is implemented as (cons nil nil).
replyThe person I was responding to (who I recall was disagreeing with me on the more general principle) said something to the effect of "well you're wrong, in common lisp that's indeed how nil is implemented".
I was skeptical and asked for proof of this claim, and they responded clearly angrily with the link to the SBCL repo and said something like "the source code is right there. You can just look it up yourself instead of being so rude. I'm no longer going to interact with you and will delete these comments in 10 minutes."
I think I looked through the source code for a few minutes, but wasn't able to find any evidence of nil being pair of itselves.
We really don’t celebrate enough how much AI has saved us from terrible SO interactions. Not being entirely serious here, because the site had its good parts, but arguing in threads or having your questions randomly eviscerated or threads closed was a hard way to learn programming.
reply