Miss Dada  🏳️‍⚧️

I think the biggest benefit here, especially for newer devs, is that they don't need to find "what is the Windows version of x". Things like rbenv or chruby are just what you use. There's a lot of docs on how to use various gems on Linux that applies to WSL

Our goal is for a Windows dev to show up on some site and see some instructions that say "open terminal, you'll see $ now type..." and not be excluded.

Seems like people (*cough*, @samsaffron) are saying WSL2 is worth it for serious Ruby development on Windows but there are major issues hindering adoption: the need for an experimental Windows build, networking quirks, differences in file locations, etc.

You don't need an experimental Windows build, that's outdated info

Roughly 1 week in, all of my issues are hardware (read keyboard layout) related, the terminal emulator not being iterm2, or https://twitter.com/sgrif/status/1230583628435845121 …. I may run into the issues you mentioned above, but I haven't yet.

Are you using wsltty, that is the only great terminal at the moment, the microsoft terminal though fast and promising is just missing too many features at the moment like mouse support.

Yeah, I'm using windows terminal. I just noticed the lack of mouse support today (which isn't something I frequently look for). At the moment my biggest gripes are the lack of clicking on urls/files to open, and that pasting multiline is funky. I'll try wsltty

https://blog.seantheprogrammer.com/preview/42sNvdyvjXctN7komL4dmq/?udate=1 … is my scratch pad of various things I've noticed while switching from mac, which may or may not turn into a blog post.