Hacker News Reader

Comment by jdauriemma | Hacker News Reader

I think they were commenting on the portability of terminal-based applications and describing remote editing as a use case. You may think it's "bad" but it's also ubiquitous, resource-efficient, and free. Can you explain to this non-Windows user why vim+tmux is painful in Windows (with or without WSL) in a local or remote setting?

View on HN

I think it's painful because terminals and ssh are just second class citizens. Dotfiles, ssh key storage etc are just not a first class concept (at least not in the same way as on linux) etc. And also things like clipboards don't work - which to a linux user might seem like a non-issue (It just never worked well) but that's a much more painful experience if you are used to it working.

Clipboards can be a hassle, for sure. Can you help me understand the impact of dotfiles / ssh key management not being a "first class concept?" How much of a time / productivity hit do you take? Thanks so much for helping me understand.

I mean the idea of config files is on one hand windows where some things work like a Linux user would expect (e.g a .gitconfig) while others obviously don’t, e.g use registry or other settings storage. Next, wsl is separate so you aren’t really sure which settings apply where. Are you using git from within wsl? Or a windows git? Is the credential manager the wsl one or one from windows? Unless one is ready to completely “jump into” wsl and ignore everything outside it has a chance of feeling coherent - but few windows users want that I’d guess.

I don’t work in windows but fwiw my clipboard and config files work flawlessly in mac and Linux. Last time I used WSL everything was working fine but it’s been a few years.

In vim in a terminal too?

Yeah I don’t recall any problems in WSL but like I said it’s been years.

Reply on news.ycombinator.com