Hacker News: sufficientsoup

New comment by sufficientsoup in "I moved my digital stack to Europe"

sufficientsoup — Wed, 13 May 2026 16:40:12 +0000

I don't think Codeberg wants to be a GitHub alternative. In particular, I don't think they want to support the use cases of someone hosting a bunch of private repos, or someone hosting commercialized code.

New comment by sufficientsoup in "Postmortem: TanStack NPM supply-chain compromise"

sufficientsoup — Tue, 12 May 2026 05:27:15 +0000

Yeah, a "seit Jahren" flashed through my mind as I read it.

New comment by sufficientsoup in "France moves to break encrypted messaging"

sufficientsoup — Sun, 10 May 2026 02:55:24 +0000

It doesn't even need to be random. What if you send an instance of a proprietary file format? Is the company required to share the spec and toolchain so that the govt can verify it (probably) isn't an encrypted message?

New comment by sufficientsoup in "How do I deal with memory leaks? (2022)"

sufficientsoup — Fri, 08 May 2026 21:07:42 +0000

I've been having fun trying out Zig recently; would recommend. FYI that they released a big batch of API changes in April (version 0.16.0) so be mindful of learning from old resources.

New comment by sufficientsoup in "Zig → Rust porting guide"

sufficientsoup — Tue, 05 May 2026 07:44:55 +0000

Wouldn’t call myself an expert in either, but I think 2 things stand out far more than anything else: 1. Rust is effectively as strict as can be in terms of ownership. In Zig you can just allocate some memory and then start slinging pointers (or slices) all over. If you’re doing this then you’re presumably doing it for mutability and you don’t strictly know where that pointer ends up once you’ve passed it on. 2. Rust’s metaprogramming is split among a couple different things (e.g. traits, macros), whereas Zig’s is unified (comptime). comptime is (at least advertised as) “just normal Zig code” and Rust macros are a great example of “this doesn’t work at all like the base language”.

#1 boils down to “can the LLM solve the pointer aliasing here?” and #2 is translating between metaprogramming paradigms. Could work but a line-by-line translation is a pipe dream.