someone asked me if I were a bot. ahahahahaa...
Any conversation
Yesterday I with help from the clanker, as an experiment, ported a web app from go+postgres+svelte to ari+duckdb+htmx served locally by busybox httpd. Itโs an analytics โdashboardโ so the stack makes sense. So far looks good. Now I work on the code in vim to make it mine. I want fewer layers of abstraction and less complexity, and this is a learning experience to that end.
I can't figure out what's leaking on my '73 F250. Shows up slowly at the back of the oil pan. It's pretty clear because I've recently changed fluids and scrubbed the engine.
It was definitely brake fluid for a while after it was overfilled but that has evened out. The oil level is steady after when checking every 10 miles or so.
I think anyway... hard to know with these ๐ฌ
azรฉrt aranyos, hogy egybลl sandbox-ba kell tenni (a Virtualbox egy sandbox), hogy szรฉt ne barmoljon mindent a gรฉpen vagy a szerveren, vagy mรกshol, azรฉrt alapvetลen bรฉkรฉs kis รกllatkรกk ezek az ai chatbotok, na
It's cute because you have to put it in a sandbox right away (Virtualbox is a sandbox) so it doesn't mess up everything on the machine or the server or anywhere else, but these AI chatbots are basically peaceful little animals, right?
WezTerm for local and remote multiplexing really is the ideal experience - it's so much better than using zellij, tmux, zmx, and friends.. I don't think they pitch this feature hard enough on their site.
I think the in-terminal multiplexers have their place - e.g. if you need to access from mobile (no WezTerm there) or on machines where you simply don't want to install WezTerm for some reason. WezTermrm could probably eliminate that last one by packaging just the mux server.
Sunk cost fallacy is no longer applicable in the age of . Now you can do broad changes without second thought, u can always revert back, without incurring the cost of doing so, since itโs all done so quickly and effortlessly.



