JIT + hotspot optimization makes JVM pretty fast, but warmup time is usually the problem. However it does look like they’re addressing startup time with improvements in this release:

- AOT compilation: https://openjdk.org/jeps/544 - ~100ms startup for ZGC: https://openjdk.org/jeps/545

This is only an issue on OpenJDK, other JVM implementations have had AOT tooling for quite some time.

Problem glasses doing problematic things.

This is not accurate, I get like 80t/s on Q3.8 27b UD Q4_K_XL on my 4090 with 3 drafts and about 110K context window, sim shows mid 20s

I get about 50 t/s with the same model on a 3090, with about 100K context. I usually set harnesses to 90k.

It would be neat to also include NVFP4 variants for the Blackwell hardware.

If someone wants contracts in C++, now they can just keep using C++. Which is good, because a lot of people and projects are stuck with C++, so the actual question is merely: can you have contracts in your project or can’t you?

what would make you think that such a creature would consider your behavior anything like a moral good, let alone have a similar system of values to yours? if anything it would probably consider it a sign of weakness or something.

I’ve always thought there should be a module-level safety property in the type system such that unsafe would be a capability granted by the user’s code.

Citizen Kane type stuff

Convenient yes, but also not just a rust thing!

You people who think this is a great thing really need to put more thought into what you propose as the migration to your better future, because what it looks like to everyone else is that you’d really love them not to able to afford heat, rent, and groceries