hey guys โบ๏ธ
Any conversation
&
โโโโโโโโโโโโโโโโโโโโโ
โโโโโโโฃโฒ โ โฑโ โโโโโโ
โ โ โฒ โ โฑ โ โ
โ โ โฒ โ โฑ โ โ
โ โ โโโโฒโโโโโโชโโโโโโฑโโโโฃ โ
โ โ โฒ โ โฑ โ โ
โ โ โฒ โ โฑ โ โ
=โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ=
โ โ โฑ โ โฒ โ โ
โ โ โฑ โ โฒ โ โ
โ โ โโโโฑโโโโโโชโโโโโโฒโโโโฃ โ
โ โ โฑ โ โฒ โ โ
โ โ โฑ โ โฒ โ โ
โโโโโโโฃโฑ โ โฒโ โโโโโโ
โโโโโโโโโโโโโโโโโโโโโ
I still don't get how now after AI coding there's people saying that contrary to common belief code wasn't a bottleneck and I realized that when I was starting to code at 10yrs ago when I was 15 and read it in a stackoverflow comment. I thought that was the common belief and still can't believe a lot of supposed senior programmers apparently believed so.
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.
An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using it.
I've been building a Markdown variant called Zd that's focused on extensibility and simplicity. I'm curious what you would change about Markdown if you were designing it from scratch, what challenges you face as a user, or what you wish were easier to do when incorporating Markdown into your own projects.





