11,388 karma · joined December 18, 2010
https://flexlists.com
Email: tycho at e-lab dot nl
Tried AI for a standalone html page snippet renderer[0].
I tried just feeding it snippets one by one and that worked, but the raymarching ones it could not get going until I gave it the dwitter github repos. Now most, but not all (simple to fix manually though), work.
Also interesting to see Claude is terrible at trying to write the art (the demos itself) and seeing what it tries to do; not surprising given the challenge.
[0] https://claude.ai/public/artifacts/d8b357df-5982-48c6-be58-7...
I got a cheap 1 year account on replit and it suffers from this of course; first few prompts yield amazing results and then it gets stuck. This is fine for me as I can fix it myself and by now I have good feeling of which type of error the current llms will just loop forever on, but it is hard to justify the pricing model of per message because for people who cannot fix it themselves and need to vibe on it; spend 50 bucks/mo for looping over one error for a day and that's that; pay more or wait or eject and go to another; I see non devs (vibe-only devs?) doing the latter so you never retain clients; they pick the good deals every month and move from one to the other.
So far only cursor is reasonable (that I know off) because it continues after the paid messages run out with the slower requests; you can go on forever.
I only helped out when it was completely stuck (twice), other than that I didn't read or check the code, just talked (voice) ideas to it when it was done while doing other (not vibe) coding while it was looping over it. I did, I guess stupidly, dictate the tech; I wanted to try Go + htmx; that probably didn't help; probably Python and/or React would've lead to better results.
Anyway; nice one! Will try.
https://github.com/tluyben/go-proxy
https://github.com/tluyben/redis-sentinel-proxy
just to make them easier to instrument for my experiments. The first one I made because after trying all tutorials on haproxy/nginx to make proxying work without the target domain being resolvable (so no dns entry until it's up), I got annoyed (nothing worked while everything only and gpt said it should work) and just did it like this. Also it makes it very easy to throw in my own, complex as I want rules and logging and telemetry (to whatever I want) at any level.
The second I needed to test an existing, not able to change (they have an old version running they cannot update at the moment, don't ask) software against a redis sentinel setup.
The main thing is that I am more and going towards having the program language as config instead of greenspun's tenth rule where everyone builds some annoying and limited 'almost (usually esoteric) programming language' as config language over time. I want that hard lifting to be done in my native language (Lisp, Go, Rust) and have the config be for ip addresses and ports only.
Featured on Arraycast: