This is happened to me before. I’ve noticed a delay in the federation such that sometimes comments recently deleted will still get votes or replies for a time. I speculate it’s because the deletion doesn’t get processed until the comment has finished being shared with other instances.

Fuck I’m old.

This is certainly an interesting feature, though my one use case has become much less relevant now that systems boot so quickly.

Perhaps if you have long running jobs and no implementation of state saving it could find applications.

Quality content.

This makes me want to cover my car entirely in retroreflectors.

When I was a kid, friends hadn’t been invented yet. We had to imagine them ourselves.

2 Duo. I remember when those came out and how multicore was still a novelty. Now my economy chip in my home desktop has 16 threads.

Yes, it does end.

Agriculture was a mistake.

Low cost, high fiber.

Boggles the mind how they work for free for a business.

I’ve worked on ground systems and it’s actually come in handy two times in five years, usually where we had a hard-to-reproduce bug. Getting the info when the problem happens can occasionally be all the difference.

Addendum: And usually we didn’t care about performance. Basically never.

When I left my last job they were using the zip file method for version control and one creative developer managed to link two versions of libc at the same time.

Software is so useful that the standard for utility is extremely low.

We test AND develop in production. Get on my level.

This is the same reason I try not to make jokes about peoples names, especially if the joke is super obvious. I imagine they feel like this guy.

Way cool! Might actually try it sometime.

With KVM performance will be quite good, but when you need to emulate cross architecture? I don’t think there are many alternatives that support the entire VM. I only know of user space tools that are focused on emulating a binary.

Call it a difference of opinion that I don’t believe it should try to be bit-accurate for floating point. But, it’s a valid position to take. There are many use cases for QEMU. In this case where we emit some host instructions I do believe it’s still within the helper function instead of inline which is not ideal. The guest code using floating point in the first place to me implies some degree of inaccuracy is permissible and this is the position that some cross architecture game emulators take. But again, I suppose it can depend what code you wish to run.

Yes indeed. I develop QEMU at work mainly implementation of new hardware as needed for my employer. It has a software emulator, but it’s not very good. It’s acceptable.

The instruction generation backend does not seem to prioritize performance. Instead, it prioritizes accuracy and ease of maintenance. There is low-hanging fruit for making it faster but there isn’t much interest in doing so for the TCG backend. The attitude seems to be that it’s good enough.

For a small example, you may find it interesting that QEMU does not implement floating point acceleration. It’s done in software even though the host has floating point instructions. It usually doesn’t attempt to use those floating point hardware facilities on the host and instead execute many hundreds of instructions to do floating point using the Berkeley software implementation. Almost never does this matter but it costs a lot of performance. Compare this to the translation performed by projects like FEX and Box64 which do and blow QEMU out of the water for specific use cases.

Another place in the emulator that could be improved is handling of executable pages or cached output of the backend code generator. The executable code caching mechanism is very simple and could probably be much more aggressive on today’s systems.

If you examine change logs, TCG really doesn’t get much TLC last time I checked. It could be a better emulator but performance outside of KVM use case is not as important to the project.

It is pretty cool! QEMU can do all kinds of interesting things, although I do wish it had better performance. High performance doesn’t appear to be a primary goal for QEMU outside of using KVM.