1,056 karma · joined May 10, 2013
Also, to what extent you designed this vs the LLM copying it?
My concern is all these vibe coded projects with huge readmes and fake GitHub stars are essentially just copying the work of others, and don’t really do anything new.
Of the bugs mentioned I think the most unforgivable one is the lossy UTF conversion. The mind boggles at that one!
Do you pair it with some orchestration (to spin up the necessary VM)?
I see that repo is two years old - are there flaws in Rust that aren’t edge cases that would make it not memory safe?
You could use a knob to slow down any game to a stop. You could also press a button to go to a console that let you change memory.
It would even figure out which bit of memory kept the number of lives of you deliberately lost a life and it could see what decremented.
None of it is mission critical - but it’s certainly something I’d use in production with a few more instances.
Networking over Tailscale works flawlessly with my Proxmox nodes at home.
They can still provide some power, but between a MacBook and official Apple power supply, they’ll keep flicking between charging and not charging.
I see an article like this about how great it is, think I might try it, then go down a rabbit hole of all the horror stories, and then give up before starting.
Or do you just check in images to GitHub and call it a day?
I was thinking of making a GitHub action that uploaded the image from a given branch, deleted it, set the URL, and finally merged only the md files to main.
I think that’s the clearest explanation of FPGAs I’ve ever seen.
Sure a phone or watch can burst into flames, but at least you’ve got a chance of dropping it or taking it off.
I also don’t see the bother of talking to your wrist rather than your hand.
Also, fillets are made using the Minkowski operation, which is super slow.