dmytrish

On the upside, Opencode has finally nudged me to learn sandboxing via bwrap in Linux and sandbox-exec on Mac.

That's what wayland-client does.

There are two kinds of memory leaks: forgotten manual freeing (all references are gone, but allocation is not) and forgetting to get rid of references that keeps an allocation alive. Both are a kind of logical error, but the first is mostly possible in languages with manual memory management. The second one is a universal logical error (only programmer knows which live references are really needed).

You don't need Mythos for that, just open the bun issue tracker and filter for "segmentation fault".

I agree with most of your points, but why would a Wayland compositor need a hypervisor at all?

That does not mean that "things as they are" is "how it's ought to be".

You don't have to love risk to build something you need.

Thanks so much for great work! I hope to finally see VisionFive 2 with enabled GPU acceleration soon.

   ~/c/t/s/zpdf (main)> zig version
   0.15.2

Sky is blue, water is wet, slop does not work.

...and it does not work. I tried it on ~10 random pdfs, including very simple ones (e.g. a hello world from typst), it segfaults on every single one.

+1, SREs can spend months during their onboarding basically reading design docs and getting to know about services in their vicinity.

Short of publicly releasing all internal documentation, there's not much that can make the AWS infrastructure reasonably clear to an outsider. Reading and understanding all of this also would be rather futile without actual access to source code and observability.

Considering that D in "ACID" stands for "durable", it's a pretty sloppy joke.

What's great about its type system? I find it severely limited and not actually useful for conveying and checking invariants.

> pass around the allocator to every function that allocates to the heap.

what prevents a library from taking an allocator, saving it hidden somewhere and using it silently?

So far, most of Zig enthusiasts look to me like people who get sugar rush from writing fast native code and are ignorant (i.e. newcomers to system programming) or arrogant (e.g. long time C programmers stubbornly stuck in their ways) enough to think that memory safety is just a question of not writing stupid bugs. Or luddites that think that programs must always be simple enough to get memory safety right.