If you knew what you were doing you could have reasoned about what your code did, though. Such is the danger of trial-by-error vibe coding. I personally closed the tab because the audio kept cutting off arbitrarily after some minutes. Not to criticise you unduly because this was a cute concept, but I hope you might take away that LLMs are not only not perfect, but are also only "good enough" if your standards for "good enough" are particularly low, and use this as motivation to learn more in the future instead of always relying on them.

I think no interaction is good for an offline pond, but I do think some tiny little bit of interaction would be nice online since it adds a touch of humanity, being able to see other people and interact with them in some small way.

Testing on a single device, or two devices, is not enough. I'm on a laptop with 96 GB ram and a Ryzen AI 9 HX PRO 370, and it's running at 3 FPS.

The crucial part is browser performance and network latency. You need to test across multiple browsers, but also evaluate frame times, CPU load, GPU load, etc. so you can make a reasonable estimate whether it's fast or not.

Then, when you realize that its not good enough, e.g. on firefox, you use firefox's profiler to see which parts are slow. LLMs would guess, probably, but you have to measure.

Welcome to software engineering.

It might be some other combination that might contribute to whether there is or isn’t lag, and I’m going to try and find what it is :)

At the end of the day, I have tools that are helping with screen-printing (and stereo photography, and other hobbies). I don't care if Brownies gathered around my computer when I was sleeping and wrote the software (to my specification).

I suppose that puts me in that group of programmers that are focused on the end-product, agnostic as to how the thing was made. I have truly never enjoyed the plumbing part of the job—just want clean tap water.

(Well, the algorithms have always fascinated with a mathematical appreciation: matrix transforms, Bloom filters, etc. Aspects like robustly handling multi-threading has always been a kind of painful Sudoku puzzle I try to do in my head—while a challenge, I sometimes would rather not hurt my brain that way. The tedium of stubbing in functions, filling them in to make a boiler-plate image cache–never very interesting.)

I don't copyright anything I do. I had some software published 36 years ago and the publisher slapped a copyright on it, but I have never done so.

Where did you get the idea that anyone was talking about trying to copyright vibe-coded tools for personal use?