Re:Introducing Surface Book 2
by stcredzero on Wednesday October 18, 2017 @12:45PM
(#15500649)
But when it comes to actually coding, it's much less "easy" than on a MBP. Some people swear by powershell but I just did not jive with having to do that when everyone else is using bash - so I'm using WSL, which has... difficulties.
I tried that, then went back to using VirtualBox in seamless mode with Lubuntu. I was very disappointed. I'm still more productive on my 2012 Macbook Pro than I am on my 2017 Windows laptop.
I've gone down that road as well, worked "ok" but as soon as the external monitor gets involved, forget about it.
Re:Introducing Surface Book 2
by stcredzero on Thursday October 19, 2017 @02:21PM
(#15510290)
If your development is terminal heavy, then you can have PuTTY on the other screen. It also works if you need to have a browser up as a part of your development. Where I get a bit tripped up, is if I need more than one screen for WebStorm or an application like that.
Re:Introducing Surface Book 2
by stcredzero on Thursday October 19, 2017 @07:47PM
(#15512512)
Long after I posted my other reply, I discovered someone's solution to multiple monitors in VirtualBox!
But when it comes to actually coding, it's much less "easy" than on a MBP. Some people swear by powershell but I just did not jive with having to do that when everyone else is using bash - so I'm using WSL, which has... difficulties. Random stuff doesn't work - SSHFS for example. Obviously anything than needs a GUI, though if you config just right you can get a display server ported through to windows through some sort of godless black magic.
I know they're still working on WSL, and if they can lock that down, I think Windows machines will be fantastic all-around dev tools, especially for a very visual developer like me (I just can't get over how great it is to whiteboard on the surface pro).