There is a lot of gray area between vibe coding and zero AI. Get over that too.

End of the day this person is solving a good problem and sharing the work. This is what we want.

Also: nagging about the specifics of the README's tone of voice, while the 600-1000MB RAM usage drops to 100-250MB seems a little childish to me.

It's still open source! Just like in the pre-AI era they are welcome to submit a PR and improve it in the way they like it. The main dev seems very open to accepting help.

▲

rplnt 17 hours ago | parent [-]

Those numbers only look good in comparison.

▲

darkwizard42 16 hours ago | parent [-]

I don't see you publishing something which further reduces the memory footprint?

Given the project is open source, have at it! See if you can help improve it instead of complaining. This is a significant improvement and a cool project!

▲

rplnt 16 hours ago | parent | next [-]

I'm not complaining and it is a cool project (from what I can tell). But I think it's fair to say 200 MB memory usage is a lot without providing source code as a proof. Just by feel when you recall what were computers capable of when they did not have 100s of MB to spare.

	▲	skydhash 15 hours ago \| parent [-]
		I remember when I was scrounging memory sticks to get to 512 mb for my windows xp setup. And I was able to play Unreal: Return to Na Pali[0] on that. [0] https://unreal.fandom.com/wiki/Unreal_Mission_Pack:_Return_t...

▲

toast0 9 hours ago | parent | prev [-]

I run actual Winamp for my music streaming, and windows task manager claims it's using 4.1 MB.

Even that seems pretty high, but whatever, but given y'all are spending hundreds of mbs, I think I'm ok. Yes, spotify has features my subscription music service doesn't have... but the one I use lets me stream with Winamp.