skysight-inc/HackerNews huggingface dataset:
> The "normal path" of least friction in Swift is a reference-counted world, while the "normal path" in Rust is the ownership-and-borrowing world.

Of course, but the borrow checker in Rust does a lot to smooth out that potential friction; and Swift will also include comparable facilities starting from Swift 6, which will finally achieve comprehensive safety including in concurrent code.

> it's really the inevitable outcome of seamless compatibility with the COM-like model of Objective-C

There's a comparable focus in Rust of getting not-quite-seamless compatibility with the COM-like model of... well duh, COM. See Microsoft's efforts at getting low-level components rewritten in Rust into their OS's.
The solution to all problems in computer science is add a new level of indirection (or abstraction).
That's about the same number for DeepSeek-V3. If you count in fp8 MFU is about 20%. MoEs are hard.

That could also be why they did fp8. If we use theoretical performance of bf16 as baseline (I know this makes few sense, but for compare with previous trainings it's convenient) the about 40% MFU, not too bad.

IOW, MoE kills training MFU and they had to do fp8 to make it not looking funny. Both DeepSeek and Meta GenAI.
Where is it manufactured? In USA or somewhere else?

If it is manufactued in other country then they might not care about heavy metals in the product.
I wrote my own language mainly to get rid of commas and colons, and I added comments while I was at it.

https://github.com/paulmooreparks/Xfer/tree/master/ParksComp...