6 ms·

One thing that kills me with this setup is having such different dev environments - I spend all day using particular tools, shortcuts, etc. on my work laptop (O

One thing that kills me with this setup is having such different dev environments - I spend all day using particular tools, shortcuts, etc. on my work laptop (OSX) then when I try to use my personal computer (can virtualize whatever OS I want, most realistic is Ubuntu for dev) to do projects the flow is totally different and it really slows me down or I worry it will take too much mental bandwidth to switch.

qz2 6y ago
I had the same problem for a bit. I used windows at work and OSX at home. The context switching was hell. I gave in eventually and use windows at home now as well. And you know what? It turned out cheaper, better and faster even though 99% of what I do is on Linux, in a VM.
- deleted 6y ago
  [deleted]
- cel1ne 6y ago
  I wrote an autohotkey script for windows to assign alt-* to most shortcuts which would require ctrl-*. Alt is physically where Macs Cmd is, so I had Alt-A for Cmd-A, Alt-F for Cmd-F, Cmd-W and so forth. This made a big difference. Also I installed EasyWindowSwitcher and assigned it to a shortcut, which gave me window-cycling like in mac.
CGamesPlay 6y ago
I wouldn't worry about this too much. I agree with a sibling comment about standardizing on one being an option, and on the other hand if you do push yourself through I think your mental plasticity will improve as a result, so: win-win what ever you decide to do. Unless you measure your performance by output, I guess ;-)
rustyminnow 6y ago
I created a personal user account on my work laptop. It keeps all of my personal and work accounts separate but reduces the effort needed to keep the environments in sync. I use different gtk, browser, and terminal themes to provide context between the accounts which helps keep things isolated
ascar 6y ago
The flipped ctrl/alt keys is the worst part for me. I really wish there was a setting in MacOS to flip them around without causing weird issues. Unfortunately, while you can flip ctrl/alt system-wide some apps already use the Linux/windows shortcuts (like terminal ctrl+c/ctrl+d for stop and exit) and then these are flipped, which drives me even more insane. The best shot is overwriting menu commands one by one, which is tiresome and still doesn't apply everywhere. I just settled to learn both, but I still see myself ctrl+c copying on mac and when alt+c when back on my windows machine. I have high hopes for WSL2 replacing MacOS or Ubuntu VM's for me, especially because Darwin is simply not a linux system and you really feel the difference once you work on natively compiled code.
- hans1729 6y ago
  > I have high hopes for WSL2 replacing MacOS or Ubuntu VM's for me, especially because Darwin is simply not a linux system and you really feel the difference once you work on natively compiled code. That's exactly what I did two weeks ago, after years of working on macos I ditched it in favor of windows. I haven't looked back since. The native WSL-integration in windows' vscode is a blessing; you open vscode, it's already connected to wsl, you write your flask-app or whatever, and can access it from windows' chrome without intermediate steps. This setup feels leaps ahead of anything I've done on macos. Bonus screenshot: https://i.imgur.com/7p5g5os.png https://i.imgur.com/7p5g5os.png
  - qz2 6y ago
    WSL integration love wears off pretty quickly I find. There are so many rough edges and broken things. While debugging a UDP server recently I discovered that any attempt to capture anything via UDP was scuppered entirely by the networking abstraction. Also the bastardised lack of services is problematic. Thus I’ve gone back to virtual box and Debian. You still can use VSCode but have to jump through some more hoops
    - shaklee3 6y ago
      Are you on wsl1 or 2?

qz2 6y ago

I had the same problem for a bit. I used windows at work and OSX at home. The context switching was hell. I gave in eventually and use windows at home now as well. And you know what? It turned out cheaper, better and faster even though 99% of what I do is on Linux, in a VM.

deleted 6y ago
[deleted]
cel1ne 6y ago
I wrote an autohotkey script for windows to assign alt-* to most shortcuts which would require ctrl-*. Alt is physically where Macs Cmd is, so I had Alt-A for Cmd-A, Alt-F for Cmd-F, Cmd-W and so forth. This made a big difference. Also I installed EasyWindowSwitcher and assigned it to a shortcut, which gave me window-cycling like in mac.

CGamesPlay 6y ago

I wouldn't worry about this too much. I agree with a sibling comment about standardizing on one being an option, and on the other hand if you do push yourself through I think your mental plasticity will improve as a result, so: win-win what ever you decide to do. Unless you measure your performance by output, I guess ;-)

rustyminnow 6y ago

I created a personal user account on my work laptop. It keeps all of my personal and work accounts separate but reduces the effort needed to keep the environments in sync. I use different gtk, browser, and terminal themes to provide context between the accounts which helps keep things isolated

ascar 6y ago

The flipped ctrl/alt keys is the worst part for me. I really wish there was a setting in MacOS to flip them around without causing weird issues. Unfortunately, while you can flip ctrl/alt system-wide some apps already use the Linux/windows shortcuts (like terminal ctrl+c/ctrl+d for stop and exit) and then these are flipped, which drives me even more insane. The best shot is overwriting menu commands one by one, which is tiresome and still doesn't apply everywhere. I just settled to learn both, but I still see myself ctrl+c copying on mac and when alt+c when back on my windows machine. I have high hopes for WSL2 replacing MacOS or Ubuntu VM's for me, especially because Darwin is simply not a linux system and you really feel the difference once you work on natively compiled code.

hans1729 6y ago
> I have high hopes for WSL2 replacing MacOS or Ubuntu VM's for me, especially because Darwin is simply not a linux system and you really feel the difference once you work on natively compiled code. That's exactly what I did two weeks ago, after years of working on macos I ditched it in favor of windows. I haven't looked back since. The native WSL-integration in windows' vscode is a blessing; you open vscode, it's already connected to wsl, you write your flask-app or whatever, and can access it from windows' chrome without intermediate steps. This setup feels leaps ahead of anything I've done on macos. Bonus screenshot: https://i.imgur.com/7p5g5os.png https://i.imgur.com/7p5g5os.png
- qz2 6y ago
  WSL integration love wears off pretty quickly I find. There are so many rough edges and broken things. While debugging a UDP server recently I discovered that any attempt to capture anything via UDP was scuppered entirely by the networking abstraction. Also the bastardised lack of services is problematic. Thus I’ve gone back to virtual box and Debian. You still can use VSCode but have to jump through some more hoops
  - shaklee3 6y ago
    Are you on wsl1 or 2?