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.
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.
if you had actually read far enough to evaluate the article on its merits, you would know that this has a hard memory consumption upper bound
Nice ideas but 100% slop
Rewriting it after that first MVP with a first round of inputs is better engineering anyway, right?
I suspect they know and care
The author cares; this is not a post-a-quick-project-as-slop-to-get-cred situation.
The entire site reeks of Claudisms and I doubt that the author even cares or knows what they are doing. The GitHub put me off immediately.
It's quite ridiculous to see such slop here and we are just going to see more of this.