I like your take on that. I also tend to think that it just diversifies market offers. Not everyone will want to vibecode their applications. Some people will still prefer to have someone create it for them.

The abstract for this paper is fire

I hate to see that these companies are just waltzing past the legal standards that should be put on them to scrutinize their data collection which could be found unconstitutional.

And I very much agree that US needs to tighten their privacy legislature.

I personally like this guys approach because he is coming at it from an angle of self hosting which I haven’t seen others do before.

I haven’t heard of them, but I love the heart behind the cause and that people seem to be passionate about it and the fact that it this is a community thing.

I will need to try iTerm's tools to see if I can do all of the same flow. Is it scriptable and does it have the same persistence features?

I will check this out. Thanks for the link!

glaucon, I agree with you. Most of feeling of "gatekeepiness" came from being a novice at using tmux and having to get used to a new workflow. tmux is as gatekeepy as vim, or other complex cli tool is - if you have never used it in the past, you might find it to be a challenge. That was all I was trying to point out. It is an entry in a diary of a noob tmux user :D

That's an awesome tool you made! For me scriptability of tmux is one of its selling points. You have taken it a step further. Love to see it!

I have thought about that. For this same reason I did not remap a lot of keys in nvim, because I still want to be able to use vim wherever I work if that is the only option.

However, I think that creating a simple git repository with rc files and configuration can be used to create a uniform experience across machines.

The git repo idea is fine for some machines, but when I log into a random customers server at 4:00AM to fix some issue that paged me, I'm not spending time cloning a repo to setup neither vim nor tmux, it just has to work.

Also the machine may not actually able to reach out onto the wider internet.

I think it depends on the use case. If I had to do what you do with random machines, I would probably need to be familiar with default tool setups as well

And for me, the most SSH’ing I do these days is into my docker containers and odds are I won’t be opening vim while I’m there.

I do like the repo idea, but I wonder if there’s an easier and maybe faster way to do it over the SSH tunnel

You may be interested in https://www.chezmoi.io/