Viewing profile — Cloudef

The way simd speeds up "compute" is indeed mainly the reason that you operate on multiple pieces of data at once.

Its possible and boy do i have a youtube channel for you https://youtu.be/ndG-6-vONNc https://youtu.be/8dfgum9XlJc

Apple does not allow running code from internet either (even if interpreted iirc) That said shipping JIT / interpreter with your program to recompile updates / parts of it sounds s…

Try reading zig code. For me its much more readable than the other languages, and does not suffer the fact go doesnt have language level errors. Local allocators are very useful an…

> Secure boot prevents tampering of your kernel and/or bootloader, nothing about Linux prevents this from being possible. By trusting another chain of trust and firmware binary blo…

Quite depends, I had times when my posix emulation of io_uring (with poll, not epoll) was faster than io_uring. For large zero-copy buffers, io_uring is king however. Also io_uring…

Symbian was really awful OS. Nokia's mistake was ignoring Maemo.

Rust unsafe is less safe than writing C code. Rust is not good language for writing "unsafe code". C++ smart pointers are really bad compared to arena allocators, and not allocatin…

Zig is not only a language. Its whole toolchain and takes freestanding as a target seriously.

Lot but not enough still. Most web tech is like that, almost there but not really. Webaudio prob being the worst one. Webgpu being weird thing that nobody really knows who it is fo…

You can let agent churn unattended if you have some sort of known goal. Write a test that should not pass and then tell the agent to come up with something that passes the test wit…

Wouldnt that be stackless (shared stack)

You are not wrong and this is indeed what zig is trying to push by making all std functions that allocate take a allocator parameter.

Trusted computing isn't about security. Its about vendors not trusting you.

Why haven't prebuilt PC market been doing this to hide the fact they are using a single RAM stick?

I see. I can not give more insightful answer here then. From personal experience, I've noticed with 0.16 with the std.Io async stuff that you cannot do: io.concurrent(foo, .{}); wh…

I think rust calls them "zero sized types".

Indeed what was referred to here is the zig build system cache.

AFAIK garbage collection is basically not implemented yet. I myself do `ZIG_LOCAL_CACHE_DIR=~/.cache/zig` so I only have to nuke single directory whenever I feel like it.

0.16 is the development version. 0.15.2 is latest release.

The language itself does not change much, but the std does. It depends on individuals, but some people rely less on the std, some copy the old code that they still need. > Are ther…

Very cool

Every paragraph in the article is exactly what LLM produces

I feel safe when claude outputs dd commands that wipe your drive to benchmark disk write speed :)

You can enable error traces for release-fast builds as well, without enabling full debug info. Though the quality of call stack of course vary depending on optimization level.