"This text may violate our content rules (harassment/threatening: 0.4593). Please revise it and try again." HOW there's no cuss words dawg let me typeeeeeee
Any conversation
de a tapasztalatok szerint a kezelลfelรผlet elfรกradรกsa elลbb-utรณbb magรกval hozza magรกnak a rendszernek az elfรกradรกsรกt, majd lassulรกsรกt, szerintem 1-2 รฉv mรบlva (amikor mรกr senki sem emlรฉkszik majd rรก), forradalmi รบjรญtรกskรฉnt visszahozzรกk a Windows 10 kezelลfelรผletรฉt Windows 12 nรฉven
but according to experience, the fatigue of the user interface will sooner or later lead to the fatigue and then the slowdown of the system itself. I think in 1-2 years (when no one will remember it anymore), they will bring back the Windows 10 user interface as a revolutionary innovation under the name Windows 12.
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.
โฆ
NIH syndrome? I am guilty of it too. I love implementing things from scratch, you learn a lot by doing so and you get to own the codebase end-to-end, so no surprises and fighting around othersโ choices. It can get exhausting too though, in the end I succumb to using off-the-shelf components because my primary goals move at a higher level.


