Hacker News: CryZe

New comment by CryZe in "Servo is now available on crates.io"

CryZe — Mon, 13 Apr 2026 15:18:11 +0000

This doesn't implement a JS engine, it's just a wrapper around boa.

New comment by CryZe in "GPT-5.4"

CryZe — Thu, 05 Mar 2026 21:42:12 +0000

I've been using both Opus 4.6 and Codex 5.3 in VSCode's Copilot and while Opus is indeed 3x and Codex is 1x, that doesn't seem to matter as Opus is willing to go work in the background for like an hour for 3 credits, whereas Codex asks you whether to continue every few lines of code it changes, quickly eating way more credits than Opus. In fact Opus in Copilot is probably underpriced, as it can definitely work for an hour with just those 12 cents of cost. Which I'm not sure you get anywhere else at such a low price.

Update: I don't know why I can't reply to your reply, so I'll just update this. I have tried many times to give it a big todo list and told it to do it all. But I've never gotten it to actually work on it all and instead after the first task is complete it always asks if it should move onto the next task. In fact, I always tell it not to ask me and yet it still does. So unless I need to do very specific prompt engineering, that does not seem to work for me.

New comment by CryZe in "What happened to WebAssembly"

CryZe — Fri, 09 Jan 2026 10:02:48 +0000

Wasm can do 64-bit integers, SIMD and statically typed GC classes.

New comment by CryZe in "What happened to WebAssembly"

CryZe — Fri, 09 Jan 2026 08:40:04 +0000

It depends. If you are compiling a high level GC language to WasmGC then there's really close to no reason why it would be larger than JS.

New comment by CryZe in "Why Zig Is Quietly Doing What Rust Couldn't: Staying Simple"

CryZe — Thu, 20 Nov 2025 09:09:29 +0000

Zig has no undefined behavior?

New comment by CryZe in "The state of SIMD in Rust in 2025"

CryZe — Thu, 06 Nov 2025 12:32:42 +0000

There are algebraic operations available on nightly: https://doc.rust-lang.org/nightly/std/primitive.f32.html#alg...

New comment by CryZe in "The state of SIMD in Rust in 2025"

CryZe — Thu, 06 Nov 2025 12:30:05 +0000

Keep an eye out for the algebraic operations on floats currently in nightly then: https://doc.rust-lang.org/nightly/std/primitive.f32.html#alg...

New comment by CryZe in "Notes by djb on using Fil-C"

CryZe — Mon, 03 Nov 2025 19:09:05 +0000

You can buffer overflow in fil-c and it won't detect it unless the entire buffer was its own stack or heap allocation with nothing following it (and also it needs to be a multiple of 16 bytes, cause that's padding that fil-c allows you to overflow into). So it arguably isn't much different from wasm.

Quick example:

typedef struct Foo {

    int buf[2];

    float some_float;

} Foo;

int main(void) {

    Foo foo = {0};

    for (size_t i = 0; i < 3; ++i) {

        foo.buf[i] = 0x3f000000;

        printf("foo.buf[%zu]: %d\n", i, foo.buf[i]);

    }

    printf("foo.some_float: %f\n", foo.some_float);

}

This overflows into the float, not causing any panics, printing 0.5 for the float.

New comment by CryZe in "Git: Introduce Rust and announce it will become mandatory in the build system"

CryZe — Sun, 21 Sep 2025 11:50:44 +0000

Ferrocene has donated their specification to the project, so there absolutely is a specification now. What you can argue is that the memory model isn‘t fully defined, but it‘s almost certainly going to land somewhere around stacked borrows or tree borrows. Arguably C doesn‘t fare much better in that regard though as it doesn‘t even properly define its pointer provenance model either and Rust is much closer to defining its.

New comment by CryZe in "Why is the Rust compiler so slow?"

CryZe — Fri, 27 Jun 2025 09:08:22 +0000

A ton of that is actually still doing codegen (for the proc macros for example).

New comment by CryZe in "Beware of Fast-Math"

CryZe — Sat, 31 May 2025 10:33:04 +0000

WebAssembly also ended up calling its set of similar instructions relaxed.

New comment by CryZe in "Show HN: I rewrote my Mac Electron app in Rust"

CryZe — Wed, 28 May 2025 18:46:57 +0000

I have an issue where I have two canvases that are overlapping and only WebKitGTK (not even just WebKit) just randomly stops showing one of the canvases.

New comment by CryZe in "JavaScript's New Superpower: Explicit Resource Management"

CryZe — Sat, 17 May 2025 13:38:34 +0000

First it was "Why Do Animals Keep Evolving into Crabs?", now it's "Why Do Programming Languages Keep Evolving into Crabs?"

New comment by CryZe in "RustAssistant: Using LLMs to Fix Compilation Errors in Rust Code"

CryZe — Fri, 02 May 2025 09:27:02 +0000

I'd love to see VSCode integrate all the LSP information into Copilot. That seems to be the natural evolution of this idea.

New comment by CryZe in "Someone at YouTube needs glasses"

CryZe — Wed, 30 Apr 2025 20:12:49 +0000

It's 1.5x3 if you have a 21:9 screen. It's so bad.

New comment by CryZe in "Someone at YouTube needs glasses"

CryZe — Wed, 30 Apr 2025 20:10:02 +0000

For me they made it so large that I can only see 3 full thumbnails. The rest don't even fit the screen anymore. https://i.imgur.com/11iI4sI.jpeg

New comment by CryZe in "Rust to C compiler – 95.9% test pass rate, odd platforms"

CryZe — Sat, 12 Apr 2025 20:20:18 +0000

There's no interpreter, I just map each instruction to equivalent Rust code. Linear memory is accessed through a trait.

The compiler is here: https://github.com/CryZe/wasm-to-rust

I have an example of a GameBoy emulator compiled from AssemblyScript to WASM to Rust here: https://github.com/CryZe/wasmboy-rs/blob/master/src/wasm.rs

New comment by CryZe in "Rust to C compiler – 95.9% test pass rate, odd platforms"

CryZe — Sat, 12 Apr 2025 11:09:59 +0000

I once implemented a WASM to Rust compiler that due to WASM's safety compiles to fully safe Rust. So I was able to compile C -> WASM -> Rust and ended up with fully safe code. Though of course, just like in WASM, the C code is still able to corrupt its own linear memory, just can't escape the "sandbox". Firefox has employed a similar strategy: https://hacks.mozilla.org/2020/02/securing-firefox-with-weba...

New comment by CryZe in "Towards fearless SIMD, 7 years later"

CryZe — Sun, 30 Mar 2025 11:39:56 +0000

Take a look into bytemuck or zerocopy. I haven't used unsafe when doing byte level manipulation in a long time.

New comment by CryZe in "Zlib-rs is faster than C"

CryZe — Sun, 16 Mar 2025 21:23:10 +0000

They are in the process of marking them safe, which is enabled through the target_feature 1.1 RFC.

In fact, it has already been merged two weeks ago: https://github.com/rust-lang/stdarch/pull/1714

The change is already visible on nightly: https://doc.rust-lang.org/nightly/core/arch/x86/fn._mm_xor_s...

Compared to stable: https://doc.rust-lang.org/core/arch/x86/fn._mm_xor_si128.htm...

So this should be stable in 1.87 on May 15 (Rust's 10 year anniversary since 1.0)