> Also when doing joins its cleaner to use the table_name.id or alias.id then table_name.table_name_id or alias.table_name_id or whatever else besides id is used However, using 'table_name.table_name_id' and then having another table with an FK that references it with the same name i.e. 'table_2.table_name_id' allows you to use a shorthand 'USING' clause instead of 'ON' in databases that support it.

Great point thanks for calling USING out. Since you end up putting table_name_id for FKs it totally makes sense to just use that in the main table. Seems I am just so accustomed to having id as the default PK over the years it become habit (my DB professor was an old time IBM-er who preached all tables will have an ID). With auto complete in just about every tool these days and ORM limitations improving will need to update my thinking on this reality. 95% of the time living in the MSSQL world so USING is not something that can even be used (I don’t think).

There's a reason Windows went from 'MyComputer' to 'This PC'.

While it's possible they meant something nefarious, I think the goal was probably just to prevent confusion around shared computers. Such confusion might seem unlikely, but when your market is as big as Microsoft's even unlikely things happen all the time.

"Our PC"

That's essentially true for all of EU. If you've ever done integration with EU central services you know what I'm talking about.

Makes sense, the EU favors architecture astronauts over profitable technology.

>tweak QEMU for performance and passthrough Any guide you could link to that covers all of this? I would like to setup a very performant windows VM.

Or a single GPU that supports SR-IOV, but AFAIK no consumer-grade GPU provides it.

IIRC Intel iGPUs support it and I read somewhere that their dGPUs do as well, but I might be misremembering.

Well that's one big feature that would entice me to buy an intel gpu in the future

This is also the only reason I ever thought of buying an Intel GPU, but then I realized "Wait, if I am buying a new GPU I can just use my old GPU for host/passthrough. I don't need a new GPU that is roughtly as good as my current one just for SR-IOV, I'd want one at least much better than my current one" (RX 5600XT, not really top but it does its job)

Intel 11th generation (Tiger Lake) clients onward have Xe* iGPUs with SR-IOV.

One thing I'm missing when modeling FSM like this is different states having different set of constraints, even if only being concerned with nullity. It's a shame having to make the field optional just because you do not have the appropriate value in the initial state of the entity.

One thing I'm missing is pkcs11 API in browsers. This seems to not make sense to US devs from what I could see but if you're in EU you can probably commiserate.

Was just thinking the same. It's also nicely ironic. Also, given the replication crisis I wonder how many of these LLM research papers are actually worth a damn and how many are research paper equivalent of AI software grift.

Can we get a model that can work this out for us?

Hammer makes no attempt to appear human

The title could probably be extended to 'You'll regret using natural keys as primary keys' and it would be right in some ways. Personally, I've come to the conclusion that it's probably best to use both surrogate and natural keys. Surrogates (IDENTITYs, UUIDs what-have-you) as PK from a technical perspective and natural key as 'PK' from a business/data modeling perspective.

Somewhere along the way the wires in my brain have crossed and started associating the word 'content' with 'litter'. So a 'content creator' became 'litterer'. It made it make sense to me why the internet feels more and more awful. It's like a park being more and more covered with litter.

I could not agree more.

“Content” comes from a world where selling adverts is the primary business and the “content” is just used as a bait or lure to attract eyeballs. The quality of the “content” is a remote concern.