kiss, chainsaw, stitches, lucky
Any conversation
a szerveren lรฉvล cookie adatokat รฉs egyรฉb nyomkรถvetล sz@rokat is a Google kezeli, รฉn nem igazรกn szoktam ezekbลl lรกtni semmit, se ip-t, se semmit, a Google inkรกbb keresลmotor, mint mestersรฉges intelligencia alkalmazรกs, de ma mรกr hibrid technolรณgiรกval dolgozik minden MI รฉs keresล
Google also manages the cookie data and other tracking s@rs on the server, I don't really see anything from these, no IP, nothing, Google is more of a search engine than an artificial intelligence application, but today all AI and search engines work with hybrid technology
Whatโs the difference between a script-kiddy and a real ? Abstraction. You can program your whole life without learning how to meaningfully abstract problems into simpler pieces that TRULY make the problem easier to understand.
Iโm not talking about design patterns or vs . These tools can help. But to really simplify something for others, you need an intellectual empathy that many simply never figure out.
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.
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.


