> why we keep trusting venture capital to be the community's stewards I have no idea.

They bought the trust.

Does appending "/genq" work?

Or use the /btw command to ask only questions

I guess appending the actual correct handwritten brainthought code is the solution here.

Well, tell that to OP, not me.

It was kind of an experiment from start. Some ideas turned out to be good, so we keep them. Some ideas turned out not to be good, so we fix them with extensions.

The problem with hardware expirements is that people owning the hardware are stuck with experiments.

Sure, but if you bought a dev board with an experimental ISA I think you knew what you were getting in to.

If your hardware is new, you get the nicest extensions though. You just don’t use the bad parts in your code.

Sure, if you are developing software for the computer you own, instead of supporting everyone.

Re-compile?

I mean, that is often what you do in embedded computing: you (re)sell hardware with one particular application.

> if your framework's value can be replicated by targeting its test suite,

Side note: this is also why SQLite's full test suite is proprietary / private

https://sqlite.org/th3.html

Except that merely surfacing them changes their behavior, like how you add that one printf() call and now your heisenbug is suddenly nonexistent

eke*

(yes, I'm dying on this hill)

The size feels like you can almost fit it in a L3 Cache-As-RAM

Sure, as long as you don't run out of `s

Hypervisor as a microkernel

Yes, there is a certain irony when you look at the cloud workloads with a type 1 hypervisor managing either serverless or container workloads.

Stripping away unused drivers (.config) and other "bloats" can get you surprisingly far.

And most importantly and TFA mentions it several times: stripping unused drivers (and even the ability to load drivers/modules) and bloat brings very real security benefits.

I know you were responding about the boot times but that's just the icing on the cake.

Mostly depends on how bloat correlates to attack surface, but you're right

But 150ms? That's boot time for dos or minix maybe (tiny kernels). 1s sure.

FreeBSD did some work to boot in 25ms.

Source: https://www.theregister.com/2023/08/29/freebsd_boots_in_25ms...

You can do <10ms. I was working to see if I could get it under 1ms, but my best was 3.5ms

for example: https://firecracker-microvm.github.io/