XLA uses MLIR very much, the interface to it is StableHLO, which is a MLIR dialect.

Ah, I'm behind the times.

> Plus, no need to build XLA using Bazel either! You’re welcome.

I don't get it, Bazel is incredible.

Many people find it complicated.

It is. The question is if it's worth the complication. The cheeky answer would be to say it is, but that's not universally true.

sidenote: it is possible to use Vulkan to map GPU memory to CPU space and even map it back to CUDA: https://x.com/steeve/status/2055042304344231978?s=20

consider it done

sadly, sandboxing is something that can't be upstreamed. this way, sandboxing is kept in zml instead of patching mesa.

as for nvtop, great program, but we missed a few features (such as sandboxing)

It looks cool and I was excited to get monitoring for the NPU on my Ryzen AI 395+, unfortunately it does not show. NPU support in linux really seems to be an afterthought.

Weird, because we tried it. It doesn’t show anything?

We use the amdsmi to get metrics. I’ll investigate.

hi, i'm the founder of https://github.com/zml/zml, very happy with Zig

Misleading title. It's about using their AI service, not the editor.

we (ZML) have been back to following Zig master since std.Io was introduced. It's not that bad tbh. Also most changes really feel like actual improvements to the language on a day to day basis.

ZML

What is even that? Not bothering to Google for it, which shows how irrelevant it is.

Good call, for bad reasons.

> At ZML, we are creating exciting AI produ[...]

tldr: they replaced using protobuf as the type system across language boundaries for FFI with true FFI

Title is as nonsensical as "We replaced Windows with ARM CPUs"

We replaced the periodic table with elements for five times the reaction.

I loved, every clickbait title should come with a tldr just like this one.

if you see an order of magnitude difference and a language involved in the title, it's something I refuse to read (unless it's an obvious choice - interpret vs compilied/jit one)