how many texts are here
Any conversation
โโโโโโโโโโโโโโโโโโโโ โโโโโโโโโโโโ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โโโ โโโโโโ โโโโโโ โโโ
โโโ โโโโโโ โโโโโโ โโโ
โโโ โโโโโโโโโโโโ โโโ โโโ
โโโ โโโโโโโโโโโ โโโ โโโ
I notice that language models are much better at programming than at writing. This is largely because, in programming, they have a closed feedback loop that allows them to find errors. Writing is much more complicated because the feedback is much more diffuse and delayed over time. In fact, it is often not well-defined.
I'm doing experiments with short attention-span students and code. Starting with python, and, oddly, now working in BASIC. As a C programmer of 40+ years, I find this aesthetically and pedagogically displeasing, but I am delighted to see them getting fully absorbed in writing
130 PRINT "You have been eaten by a bear!" : GOTO 900. Yes there is spaghetti, but it's their spaghetti and they seem to take delight in debugging it. Python will come later. 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.

