4 ms·

Just looked at this and wondered, how much Claude AI slop went into this project and unsurprisingly a lot of it. The entire site reeks of Claudisms and I doubt

by rvz 1mo ago

Just looked at this and wondered, how much Claude AI slop went into this project and unsurprisingly a lot of it. 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.

yjftsjthsd-h 1mo ago
It's a good idea, and the implementation works. Are there actual problems, or are you just complaining that AI was used?
- rvz 1mo ago
  > 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 1mo ago
    > 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.
  - kclejeune 1mo ago
    you’re on hacker news, since when has “making sense to use in the long run” ever been the point? 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
wrxd 1mo ago
Have a look at the submissions from that websites. The quantity alone indicates that the author is vibing full steam. Nice ideas but 100% slop
- teroshan 1mo ago
  That being said, isn't it the best use-case for slop? Generating working, interactive ideas to sell an idea and kick-start a discussion to see if it's anything worth pursuing? Rewriting it after that first MVP with a first round of inputs is better engineering anyway, right?
Powdering7082 1mo ago
The author's talks on nix go back to 2020: https://fzakaria.com/talks https://fzakaria.com/talks I suspect they know and care
tomberek 1mo ago
The ability to quickly try out and verify ideas is valuable. This would have taken immensely more time to get to a stage to reasonable verify or dismiss as an idea otherwise. This saves time for builders. The author cares; this is not a post-a-quick-project-as-slop-to-get-cred situation.

by rvz 1mo ago

yjftsjthsd-h 1mo ago

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

rvz 1mo ago
> 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 1mo ago
  > 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.
- kclejeune 1mo ago
  you’re on hacker news, since when has “making sense to use in the long run” ever been the point? 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

wrxd 1mo ago

Have a look at the submissions from that websites. The quantity alone indicates that the author is vibing full steam. Nice ideas but 100% slop

teroshan 1mo ago
That being said, isn't it the best use-case for slop? Generating working, interactive ideas to sell an idea and kick-start a discussion to see if it's anything worth pursuing? Rewriting it after that first MVP with a first round of inputs is better engineering anyway, right?

Powdering7082 1mo ago

The author's talks on nix go back to 2020: https://fzakaria.com/talks https://fzakaria.com/talks I suspect they know and care

tomberek 1mo ago

The ability to quickly try out and verify ideas is valuable. This would have taken immensely more time to get to a stage to reasonable verify or dismiss as an idea otherwise. This saves time for builders. The author cares; this is not a post-a-quick-project-as-slop-to-get-cred situation.