5 ms·

I agree. I'm (mostly) a Windows user, and the one reason I'm constantly thinking of moving to OSX as my primary OS is the amount of command-line tooling that is

I agree. I'm (mostly) a Windows user, and the one reason I'm constantly thinking of moving to OSX as my primary OS is the amount of command-line tooling that is available in the system. Everything new is always there first. I've started feeling that I was holding back by staying on Windows, even if using Mingw daily. This might be the thing that saves Windows as a dev machine for me. I'm a heavy cmd/powershell user but I'd migrate to bash in an instant.

avtar 11y ago
> I'm constantly thinking of moving to OSX as my primary OS is the amount of command-line tooling that is available in the system. Everything new is always there first. Having had OS X, Windows, and various Linux distributions as my primary operating systems I would consider having an Arch Linux VM kicking around if you want all the packages in the world, maintained fairly well.
- whatever_dude 11y ago
  I've done so in the past, but it becomes cumbersome to manage shared folders. The ability to have everything shared and your driver naturally working under /mnt/ - essentially replacing cmd with bash and its tools - is a big deal for me. Using editing/managing/design tools in Windows build with a build/deploy system in bash, and no middle man... that'd be the day.
  - Scarbutt 11y ago
    You don't use shared folders with your linux VM, you ssh to it, and use tmux/(vim|emacs) ;)
swah 11y ago
Me too - but why not a Linux VM or a VPS? Its mostly for textual usage, no? (My own answer is that cheap VPSes are 150ms away from me, and with Virtualbox I had a few problems, always related to Windows file permissions yada yada yada...)
- whatever_dude 11y ago
  Same. At some point managing permissions and sharing and VMs just becomes a pain. If I can just drop to bash and access my file system... that's all I need/want.
- matt_wulfeck 11y ago
  150ms sucks when you're working with multi GB files and packages. Also network security is not ideal. Nothing beats running and developing on localhost.

avtar 11y ago

> I'm constantly thinking of moving to OSX as my primary OS is the amount of command-line tooling that is available in the system. Everything new is always there first. Having had OS X, Windows, and various Linux distributions as my primary operating systems I would consider having an Arch Linux VM kicking around if you want all the packages in the world, maintained fairly well.

whatever_dude 11y ago
I've done so in the past, but it becomes cumbersome to manage shared folders. The ability to have everything shared and your driver naturally working under /mnt/ - essentially replacing cmd with bash and its tools - is a big deal for me. Using editing/managing/design tools in Windows build with a build/deploy system in bash, and no middle man... that'd be the day.
- Scarbutt 11y ago
  You don't use shared folders with your linux VM, you ssh to it, and use tmux/(vim|emacs) ;)

swah 11y ago

Me too - but why not a Linux VM or a VPS? Its mostly for textual usage, no? (My own answer is that cheap VPSes are 150ms away from me, and with Virtualbox I had a few problems, always related to Windows file permissions yada yada yada...)

whatever_dude 11y ago
Same. At some point managing permissions and sharing and VMs just becomes a pain. If I can just drop to bash and access my file system... that's all I need/want.
matt_wulfeck 11y ago
150ms sucks when you're working with multi GB files and packages. Also network security is not ideal. Nothing beats running and developing on localhost.