It's a good idea, and the implementation works. Are there actual problems, or are you just complaining that AI was used?

▲

rvz 27 minutes ago | parent [-]

> It's a good idea, and the implementation works.

Just because something "works" doesn't not mean it makes sense to use in the long run. It is incredibly memory inefficient and will cause the user's machine to crash. Not everyone is running the latest ThinkPad or Macbook with 64GB RAM.

Without those considerations, I believe it is complete AI slop.

	▲	yjftsjthsd-h 18 minutes ago \| parent [-]
		> It is incredibly memory inefficient and will cause the user's machine to crash. Not everyone is running the latest ThinkPad or Macbook with 64GB RAM. Thankfully, you don't need that: > Lastly, we have an upper-bound on the size of the closure we can fetch. The whole closure has to fit in tab memory, which is set to a hard limit of ~1.5GiB as of now and WebAssembly has a hard limit of 4GiB as it is a 32-bit address space. And it works fine on my 3-year-old phone with 8G of RAM, so I think your complete dismissal of VMs is excessive.