CryZe

6 ms·

1.
by CryZe 2mo ago
Seems to match the pareto frontier on Artificial Analysis as well. Terra is nowhere on it.
2.
by CryZe 3mo ago
> 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 as well.
3.
by CryZe 5mo ago
This doesn't implement a JS engine, it's just a wrapper around boa.
4.
by CryZe 7mo ago
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
5.
by CryZe 8mo ago
Wasm can do 64-bit integers, SIMD and statically typed GC classes.
6.
by CryZe 8mo ago
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.
7.
by CryZe 10mo ago
Zig has no undefined behavior?
8.
by CryZe 10mo ago
There are algebraic operations available on nightly: https://doc.rust-lang.org/nightly/std/primitive.f32.html#alg...
9.
by CryZe 10mo ago
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...
10.
by CryZe 11mo ago
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 allow
11.
by CryZe 1y ago
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
12.
by CryZe 1y ago
A ton of that is actually still doing codegen (for the proc macros for example).
13.
by CryZe 1y ago
WebAssembly also ended up calling its set of similar instructions relaxed.
14.
by CryZe 1y ago
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.
15.
by CryZe 1y ago
First it was "Why Do Animals Keep Evolving into Crabs?", now it's "Why Do Programming Languages Keep Evolving into Crabs?"
16.
by CryZe 1y ago
I'd love to see VSCode integrate all the LSP information into Copilot. That seems to be the natural evolution of this idea.
17.
by CryZe 1y ago
It's 1.5x3 if you have a 21:9 screen. It's so bad.
18.
by CryZe 1y ago
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
19.
by CryZe 1y ago
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 em
20.
by CryZe 1y ago
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 st
21.
by CryZe 1y ago
Take a look into bytemuck or zerocopy. I haven't used unsafe when doing byte level manipulation in a long time.
22.
by CryZe 2y ago
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
23.
by CryZe 2y ago
That was the time we learned about the changes to the block feature.
24.
by CryZe 2y ago
I still don't know why that isn't just provided for you.
25.
by CryZe 2y ago
> ability to use 64 bit types more easily Those are available on wasm32 just the same.
26.
by CryZe 2y ago
> It's not like you can rely on Rust references and C pointers being identical in the ABI either. You absolutely can rely on that: https://doc.rust-lang.org/reference/type-layout.html#pointer... In fact, it&#x2
27.
by CryZe 2y ago
Only about 1/3 of those are language features. Out of those a ton are #[cfg] related (i.e. being able to more accurately doing conditional compilation), const (lifting limitations with compile time evaluation), documentation, architect
28.
by CryZe 2y ago
> Maybe not yet, but it is heading in that direction About 95% of the unstable features lift limitations that most people expect not to be there in the first place. I'm not aware of all too many that aren't like that.
29.
by CryZe 2y ago
> huge pain in the ass Maybe if you structure your code weirdly? I haven't encountered a major borrow checker issue that I couldn't easily resolve in many years.
30.
by CryZe 2y ago
I wouldn't be surprised if they showed up at the maintainer's house even.

More ›