abuldauskas

5 ms·

1.
by abuldauskas 8mo ago
I also noticed it. On million-points. MacBook Pro M2 on Firefox Nightly 148.0a1 (2026-01-09) (aarch64)
2.
by abuldauskas 6y ago
I don't really understand how this approach breaks what you are describing. All I'm saying is that instead of hooks API being imported from React at global scope it could be provided as inputs into the components directly. They wo
3.
by abuldauskas 6y ago
My only issue with Hooks has been that they are not inputs into the component. It's a step in the right direction of making React more functional I would just preferred less magic, personally. function Component(props, { useState,
4.
by abuldauskas 8y ago
Node 11 now comes with v8 v7.0, does this mean Webassembly threads are supported? Or are they behind a flag?
5.
by abuldauskas 8y ago
I have not, this has been requested quite a bit though. My focus is currently on making sure the toolchain is stable and performant itself. It's likely that the performance of the compiled code is on par with other wasm vs JS compariso
6.
by abuldauskas 8y ago
That's the thing though. We are all "us" here. We can all compile whatever we want to WebAssembly, that's the point of WebAssembly. One way of doing things doesn't take away from another.
7.
by abuldauskas 8y ago
Escaping JavaScript is not a perspective shared by all (most?), though. It's has been a weird and interesting project, but that's not really a bad thing is it.
8.
by abuldauskas 8y ago
I wrote/maintain Walt. This question comes up a bunch. The two projects are really similar no doubt. I can't speak for AssemblyScript, but my own motivation was simple. I wanted to learn WebAssembly and I wanted an accessible plat
9.
by abuldauskas 8y ago
One of my major pain points with GitLab was its API. The lack of coherent API design ultimately made me lose hope in the product. For example I think it still lacks an ability to create threads on MRs. Until recently it wasn't possible