Viewing profile — CryZe

Seems to match the pareto frontier on Artificial Analysis as well. Terra is nowhere on it.

> THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! This seems to be a common Chromium problem across tons of software. GitHub has the same issue with its spinners, VSCode a…

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

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 backgr…

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

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.

Zig has no undefined behavior?

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

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...

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 …

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 almo…

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

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

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.

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

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

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

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

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 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. Thou…

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

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/s…

That was the time we learned about the changes to the block feature.