The kind of people GP is referring to refuse to actually learn from this. I've had several coworkers over the last 15 years that absolutely refuse to 'learn to fish'.
I think it shows exactly the opposite of the second. Even with the availability of checklists, and instructions to use them, people won't and don't actually use them consistently.
'With enough eyes, all bugs are shallow' and AI is an automatable eye that looks at things we can tell nobody has seriously looked at before. It's not a panacea, there will be lots of false positives, but there's value there that we clearly aren't getting by 'just telling humans to use the tools available'.
See also: modern practices and sanitizers and tools and test frameworks to avoid writing memory errors in C, and the reality that we keep writing memory errors in C.
This doesn't follow at all. The game received _excellent_ reviews prior to release. It's currently the second best reviewed PC game of the year on metacritic [1] (an aggregator with some problems but I don't think this is controversial).
Exactly contrary to your point, both Clair Obscur and Blue Prince (#1) got excellent reviews in the days leading up to release leading to people on e.g. Reddit saying "this game came out of nowhere and it has amazing reviews, I'm excited".
There isn't one, there are hundreds. Given that you end up on a small fandom wiki, you have no idea where 'the better community' is. You go to your search engine of choice and start clicking random wikis hoping at least one other one has decent info (most are useless).
As a concrete example, Path of Exile moved to https://www.poewiki.net/ (which is a single MediaWiki instance not associated with a larger network). The content is quite good but it took probably 18 months for it to start reliably appearing in google search results.
> What you need is volatile read/write or load/store intrinsics. When you have those, you can express what's actually possible on a hardware platform, and not inadvertently enable people to write nonsense in your language...
Firefox has all of this except the date. `about:config` lists all config values, values in bold do not match their default or do not exist by default, values can be reverted with one click, and there's a checkbox to filter out unmodified items.
Credit cards have by far the best in-person UX of the options that I am presented, tap my card or phone and leave and they're accepted everywhere in practice (my debit card is not).
The 'cardholder can always reverse any charge' behavior is also nice once every few years.
Not a direct compiler optimization, but consider memcpy() vs memmove() as an example. If you know two regions of memory do not overlap you can call memcpy() for a direct optimized copy, but if they overlap you must call memmove() and introduce an intermediate copy.
The article shows that federation delivers data to Meta even if you personally don't use Threads, but I agree with your point.
If you want to control distribution of your data, don't join a federation designed to distribute data. Trying to blacklist nodes in a graph that you don't control is not a solution.
Information wants to be free, if you post something to a social graph assume everyone in the graph can see it forever.
This is such an obviously good solution to covering API costs that it becomes clear that the actual goal is not to cover API costs, but something else - probably to kill third party apps.
I happily paid for Premium for years, I've gotten a lot of value out of Reddit and I wanted to make sure that they got money even though I blocked all their ads. I cancelled when they announced these API changes since it's the only leverage I have.
A paid ad-free version of their site isn't really good enough though. To keep me happy I need to be able to keep using third party apps on mobile, maybe something like 'exempt requests from Premium accounts from API billing'.
Non-managers, they aren't responsible for anyone but themselves. I know nothing of Meta's specific titles but I'd expect that e.g. the first level of full time engineering manager would convert to a full time senior or staff engineer.
Bloomberg's comdb2 does something similar, using the SQL grammar and query planner but swapping out the storage layer. To quote from their paper:
"In SQLite a query plan is compiled into a bytecode program that is executed by a virtual machine, named Virtual DataBase En-gine (VDBE)... In the original SQLite implementation the VDBE operates on the real B-trees of the database... In contrast the Comdb2 VDBE operates on the cdb2 abstraction of a table during the OCC phase of transaction execution..."