azakai

10 ms·

61.
by azakai 9mo ago
Yes, and these tools are already being used defensively, e.g. in Google Big Sleep https://projectzero.google/2024/10/from-naptime-to-big-sleep... List of vulnerabilities found so far: https://issuetrack
62.
by azakai 9mo ago
> For example what, exactly, is a "high-utility response to harmful queries?" It's gibberish. It sounds like it means something, but it doesn't actually mean anything. (The article isn't even about the degree of
63.
by azakai 9mo ago
Sorry, yes, I meant PNaCl. > I don't see an issue with shipping uArch specific assembly, nowadays you only have 2 really in heavy use today, That is true today, but it would prevent other architectures from getting a fair shot. Or,
64.
by azakai 9mo ago
> Why should we aim to increase portability? There's a lot of unstated ideological assumptions underlying that goal, which not everyone shares. As far back as I can remember well (~20 years) it was an explicitly stated goal to keep
65.
by azakai 9mo ago
> What does "portable" mean? In the context of the web, portability means that you can, ideally at least, use any browser on any platform to access any website. Of course that isn't always possible, as you say. But adding
66.
by azakai 9mo ago
Yes, that puzzles me too. Not only do I not know what the author means, I'm not sure what it could mean: teaching material for wasm is generated by many independent people, each for their own tools and purposes. There is no organizat
67.
by azakai 9mo ago
Performance. JS can be as fast as wasm, but generally isn't on huge, complex applications. Wasm was designed for things like Unity games, Adobe Photoshop, and Figma - that is why they all use it. Benchmarks on such applications usually
68.
by azakai 9mo ago
> WASM seems to exist mostly because Mozilla threw up over the original NaCL proposal (which IMO was quite elegant). They said it wasn't 'webby', a quality they never managed to define IMO. No, Mozilla's concerns at t
69.
by azakai 9mo ago
It is totally fine if most people don't relate to wasm - it's good for some things, but not most things. As another example, most web devs don't use the video or audio tag, I'd bet, and that's fine too. Media, and w
70.
by azakai 9mo ago
To be fair, Native Client achieved much of its speed by reusing LLVM and the decades of work put into that excellent codebase. Also, Native Client started up so fast because it shipped native binaries, which was not portable. To fix that, P
71.
by azakai 9mo ago
It is easy to make benchmarks where JS is faster. JS inlines at runtime, while wasm typically does not, so if you have code where the wasm toolchain makes a poor inlining decision at compile time, then JS can easily win. But that is really
72.
by azakai 9mo ago
No, doctors still recommend limiting the intake of cholesterol in food, and also saturated fat. See: https://en.wikipedia.org/wiki/Cholesterol#Medical_guidelines... https://www.heart.org/en/news&#x
73.
by azakai 10mo ago
Have you tried Photoshop's online version that runs in a Web browser? (it uses wasm)
74.
by azakai 10mo ago
This is certainly possible: Break up large functions, and then the bounded maximum function size can be your O(1) chunk size, to be processed in a streaming manner without dynamic allocation. However, breaking up huge functions (or skipping
75.
by azakai 10mo ago
Saying people shouldn't create open source code because AI will learn from it, is like saying people shouldn't create art because AI will learn from it. In both cases I get the frustration - it feels horrible to see something you
76.
by azakai 10mo ago
ES-1 is the most important figure, though? As you say, it is a summary, and the authors consider it their best estimate, hence they put it first, and in the executive summary. Figure 1.1 does show a single source from 2018 (Shehabi et al) t
77.
by azakai 10mo ago
The first chart in your link doesn't show "flat" usage until 2022? It is clearly rising at an increasing rate, and it more than doubles over 2014-2022. It might help to look at global power usage, not just the US, see the fir
78.
by azakai 10mo ago
Looks like those sizes could be improved significantly, as the builds include names etc. I would suggest linking with emcc -O3 (and maybe even adding --closure 1 ) edit: actually the QuickJS playground looks already optimized - just the M
79.
by azakai 10mo ago
> features no one needed (GC) WasmGC is absolutely necessary for languages like Dart, Kotlin, and Java, which are all using it right now successfully. But I get that if you're compiling C or Rust then it might seem like it isn'
80.
by azakai 10mo ago
That is incorrect about function pointers: The VM does check that you are calling the right function type, and it will trap if the type does not match. Here it is in the spec: > The call_indirect instruction calls a function indirectly
81.
by azakai 10mo ago
Your general point stands - wasm's original goal was mainly sandboxing - but 1. Wasm does provide some amount of memory safety even to compiled C code. For example, the call stack is entirely protected. Also, indirect calls are type-
82.
by azakai 1y ago
Some data on how badly he torched his consumer base: a Yale study says Tesla lost 1.26 million US sales due to Musk's politics. https://www.usatoday.com/story/cars/news/2025/10/28/tesla-lo.
83.
by azakai 1y ago
0% slower means "the same speed." The same amount of seconds. 10% slower means "takes 10% longer." 10% more seconds. So 45% slower than 2 seconds is 1.45 * 2 = 2.9 seconds.
84.
by azakai 1y ago
The data here is interesting, but bear in mind it is from 2019, and a lot has improved since.
85.
by azakai 1y ago
It might just be that we evolved it first. Someone has to (if anyone does).
86.
by azakai 1y ago
The Cranelift website does have that quote, but the linked paper says > The resulting code performs on average 14% better than LLVM -O0, 22% slower than LLVM -O1, 25% slower than LLVM -O2, and 24% slower than LLVM -O3 So it is more like
87.
by azakai 1y ago
Hi! Yeah, certainly compiler smarts can remove many bounds checks (in particular for small deltas, as you mention), hoist them, and so forth. Maybe even most of them in theory? Still, there are common patterns like pointer-chasing in linked
88.
by azakai 1y ago
Great, thanks for the info!
89.
by azakai 1y ago
Sorry about binaryen.js - those JS/TS bindings could be a lot better, and better documented, but priorities are generally focused on improving optimizations in core Binaryen. That is, most work in Binaryen is on improving wasm-opt whic
90.
by azakai 1y ago
> garbage collection was implemented by my colleague Nick Fitzgerald a few years ago The wasm features page says it is still behind a flag on wasmtime (--wasm=gc). Is that page out of date?

More ›