4 ms·

> No, only containerized things need to be in a container. For everything else you are just using Windows except it feels more Linux like with git bash and has

> No, only containerized things need to be in a container. For everything else you are just using Windows except it feels more Linux like with git bash and has most basic Linux tools. But developer focused software is trash on Windows, if I want to remain productive I need a Linux environment so I can just run stuff without having to fuck around to configure it for Windows and what not.

osigurdson 1y ago
Maybe but curious as to what you mean by developer focused software.
- CaptainOfCoit 1y ago
  Well, I guess docker is as good of an example as anything. Using it on Linux is a much smoother experience than Windows+VM/WSL2 could ever be.
  - osigurdson 1y ago
    Oh ok. If you use podman instead there isn't as much friction. Just type "podman" instead of "docker" as the commands are the same. winget install -e --id RedHat.Podman podman run --it --rm -p 8000:8000 .. image For gitbash, add a new profile in Windows Terminal and find "bash.exe" in Program Files\Git (sorry I can't remember the details and not on Windows right now). Once you have this you can use normal Linux commands, setup a .bashrc, ls, cd ~, vi, etc. Anyway, food for thought in case you want to try a different workflow one day.
    - CaptainOfCoit 1y ago
      > winget install -e --id RedHat.Podman && podman run --it --rm -p 8000:8000 .. image Where exactly does this run? Podman/Docker makes no difference, doesn't it? You still need to run a VM (WSL2 on Windows), so might as well run those directly in the WSL2 environment I already have? But again, docker in WSL2 doesn't work as directly on Linux, for whatever reason. > For gitbash, add a new profile in Windows Terminal and find "bash.exe" in Program Files\Git (sorry I can't remember the details and not on Windows right now). Once you have this you can use normal Linux commands, setup a .bashrc, ls, cd ~, vi, etc. Been there and tried that, and "git bash" on Windows is probably the worst mixmatch, and bunch of tooling gets confused when the shell is bash but the actual host is Windows.
      - osigurdson 1y ago
        It sounds like you are happy with your current setup. Enjoy!

osigurdson 1y ago

Maybe but curious as to what you mean by developer focused software.

CaptainOfCoit 1y ago
Well, I guess docker is as good of an example as anything. Using it on Linux is a much smoother experience than Windows+VM/WSL2 could ever be.
- osigurdson 1y ago
  Oh ok. If you use podman instead there isn't as much friction. Just type "podman" instead of "docker" as the commands are the same. winget install -e --id RedHat.Podman podman run --it --rm -p 8000:8000 .. image For gitbash, add a new profile in Windows Terminal and find "bash.exe" in Program Files\Git (sorry I can't remember the details and not on Windows right now). Once you have this you can use normal Linux commands, setup a .bashrc, ls, cd ~, vi, etc. Anyway, food for thought in case you want to try a different workflow one day.
  - CaptainOfCoit 1y ago
    > winget install -e --id RedHat.Podman && podman run --it --rm -p 8000:8000 .. image Where exactly does this run? Podman/Docker makes no difference, doesn't it? You still need to run a VM (WSL2 on Windows), so might as well run those directly in the WSL2 environment I already have? But again, docker in WSL2 doesn't work as directly on Linux, for whatever reason. > For gitbash, add a new profile in Windows Terminal and find "bash.exe" in Program Files\Git (sorry I can't remember the details and not on Windows right now). Once you have this you can use normal Linux commands, setup a .bashrc, ls, cd ~, vi, etc. Been there and tried that, and "git bash" on Windows is probably the worst mixmatch, and bunch of tooling gets confused when the shell is bash but the actual host is Windows.
    - osigurdson 1y ago
      It sounds like you are happy with your current setup. Enjoy!