5 ms·

I've also tried to use a Linux VM on Widnows due to issues with Node, paths in various Scala libs, and a dozen other problems. Cygwin works for 50%, but not fo

I've also tried to use a Linux VM on Widnows due to issues with Node, paths in various Scala libs, and a dozen other problems. Cygwin works for 50%, but not for everything. I've tried Win 10 with Subsystem for Linux (Ubuntu Bash) and unfortunately it is not even close to production ready. Besides, I'm terribly disappointed with Win 10 after having been really happy with Windows 7 since its release. Running a few Java and Javascript projects in IntelliJ on a VM is an exercise in frustration, even on a very powerful Dell Precision with an I7, SSD, and 32 GB of ram. It works somewhat, but I'm very happy with my work provided 2015 MB Pro with only 16GB of ram. With Brew, Docker, etc. everything works great. If work hadn't paid for the Mac, I don't think I'd buy a new model due to the price and lack of upgradability, no escape key, ports, etc. That being said, I've just installed Fedora 25 on a second m2 drive I put into my one Win 10 laptop. So far it is pretty good for dev work. It's not perfect, but it's approaching usability with a small Win VM for Office.

slantyyz 10y ago
Have you trued ConEMU/CMDer? For my uses, I found it to be an adequate replacement for the terminal in OSX. Outside of "watch" not working properly in Windows, the stuff I've done in Node has worked fine, but I probably do simple stuff compared to most.
- WorldMaker 10y ago
  "watch" works great in Node when "natively" installed, rather than Bash on Ubuntu on Windows. Natively installed Node is a great development experience on Windows these days (just make sure you install a version with NPM >= 3, which is now no longer an issue as even current LTS has NPM >= 3). On the flipside, Ruby remains a nightmare to install natively and Ubuntu Bash is the easiest way to work with it. There I really do miss having a working "watch" for Jekyll builds.
  - slantyyz 10y ago
    >> Ruby remains a nightmare to install natively I cheated and used RubyInstaller for Windows, and it's worked great for me for the past couple of years, but I guess it really comes down to how you use it and what you need.
    - WorldMaker 10y ago
      I always seem to need to install native dependencies for Ruby (often dependencies of dependencies of github-pages; I know github-pages seems to be trying to remove native dependencies, but as with all dependency cleanup games, it seems like a bit of whack-a-mole) and installing the DevKit and getting the DevKit working and getting the native dependencies to install has been a different beast every time I've ever tried to do it. Eventually I always seemed to hit a non-cross-platform-capable makefile somewhere, and could only throw my hands up in despair and give up. Definitely a lot easier in the Ubuntu on Windows userspace. (Though I was still fighting some weird fires with rvm and whatnot. Given I pretty much only ever need Ruby for github-pages/Jekyll work, I'm sure there is much I don't know about Ruby and a lot of the pain of the Ruby ecosystem to me is simply the fact that of the major 'modern web dev' ecosystems [node, python, ruby] it is the one I know and use the least.)
      - bitcrazed 10y ago
        Yeah, native dependencies in Ruby Gems, node modules, etc., are the bane of the open-source developer. This is why we built the Windows Subsystem for Linux: Sometimes, you've just gotta run native Linux code or code that expects a genuine Linux environment.
  - slantyyz 10y ago
    btw, what do you mean by Node when "natively" installed. I used the Windows installer from the node site. Is that what you meant? The issue I get with watch is that it doesn't properly detect added files in a watched subfolder, although changes and deletions are detected with no issue.
    - WorldMaker 10y ago
      Interesting, I've not noticed that problem, but just realized in my typical usage of a watch in Node I don't usually add new files.
Klathmon 10y ago
I have also been disappointed with the Bash-On-Ubuntu-On-Windows thing from MS. It seems like they fixed a lot of the frustrating issues recently but it's gonna take a few months for it to get to stable so it's still a non-option for me as well. But i've had extremely good results by using the terminal and "GNU-ish tools" provided by "git for windows" which has worked fantastically. I can interop with the windows system perfectly, I get all my favorite tools like git, cat, sed, grep, awk, all the bash shell stuff, and ssh and more, and it looks a lot nicer than the default cmd. Until the interop with the "host" windows system is better, and they push the fixes to the missing features like inotify and some others, I'm gonna stick with that.
- bitcrazed 10y ago
  Hey there: PM for Windows Console & Bash here: If you're running Win10 Anniversary Update (AU), know that this was our first formal release of the Windows Subsystem for Linux (WSL) and was, as we made very clear prior to release, missing several key features and capabilities. However, we wanted to get it into users' hands ASAP so that we could asked the community for help to identify what worked and what didn't. And the community leapt to help-out, resulting in literally hundreds of fixes to WSL and to the Windows Console. We've continued to release improvements over the last several months through the Windows Insider builds (release notes: https://msdn.microsoft.com/en-us/commandline/wsl/release_notes https://msdn.microsoft.com/en-us/commandline/wsl/release_not...), and have posted updates and highlights via our blog: https://blogs.msdn.microsoft.com/commandline/ https://blogs.msdn.microsoft.com/commandline/. All these improvements have resulted in Bash/WSL now being very, VERY usable as a real-world dev environment. We've a few more fixes and improvements in the pipe that'll emerge in the next few weeks, but you can feel confident that Bash/WSL is rapidly becoming a viable, highly productive, genuine, Linux compatible environment for running your favorite *NIX-first tools, platforms and technologies. HTH.
pixelcloud 10y ago
Try using Linux with a Windows VM (if required). I have a computer running Arch Linux + Plasma and it is quite nice. With a bit of tweaking you can get a OSX like or Windows like desktop environment. I will use the Windows VM to connect to a VPN and run work applications that require windows, but I can get my email and documents easily through Office365 90% of the time.

slantyyz 10y ago

Have you trued ConEMU/CMDer? For my uses, I found it to be an adequate replacement for the terminal in OSX. Outside of "watch" not working properly in Windows, the stuff I've done in Node has worked fine, but I probably do simple stuff compared to most.

WorldMaker 10y ago
"watch" works great in Node when "natively" installed, rather than Bash on Ubuntu on Windows. Natively installed Node is a great development experience on Windows these days (just make sure you install a version with NPM >= 3, which is now no longer an issue as even current LTS has NPM >= 3). On the flipside, Ruby remains a nightmare to install natively and Ubuntu Bash is the easiest way to work with it. There I really do miss having a working "watch" for Jekyll builds.
- slantyyz 10y ago
  >> Ruby remains a nightmare to install natively I cheated and used RubyInstaller for Windows, and it's worked great for me for the past couple of years, but I guess it really comes down to how you use it and what you need.
  - WorldMaker 10y ago
    I always seem to need to install native dependencies for Ruby (often dependencies of dependencies of github-pages; I know github-pages seems to be trying to remove native dependencies, but as with all dependency cleanup games, it seems like a bit of whack-a-mole) and installing the DevKit and getting the DevKit working and getting the native dependencies to install has been a different beast every time I've ever tried to do it. Eventually I always seemed to hit a non-cross-platform-capable makefile somewhere, and could only throw my hands up in despair and give up. Definitely a lot easier in the Ubuntu on Windows userspace. (Though I was still fighting some weird fires with rvm and whatnot. Given I pretty much only ever need Ruby for github-pages/Jekyll work, I'm sure there is much I don't know about Ruby and a lot of the pain of the Ruby ecosystem to me is simply the fact that of the major 'modern web dev' ecosystems [node, python, ruby] it is the one I know and use the least.)
    - bitcrazed 10y ago
      Yeah, native dependencies in Ruby Gems, node modules, etc., are the bane of the open-source developer. This is why we built the Windows Subsystem for Linux: Sometimes, you've just gotta run native Linux code or code that expects a genuine Linux environment.
- slantyyz 10y ago
  btw, what do you mean by Node when "natively" installed. I used the Windows installer from the node site. Is that what you meant? The issue I get with watch is that it doesn't properly detect added files in a watched subfolder, although changes and deletions are detected with no issue.
  - WorldMaker 10y ago
    Interesting, I've not noticed that problem, but just realized in my typical usage of a watch in Node I don't usually add new files.

Klathmon 10y ago

I have also been disappointed with the Bash-On-Ubuntu-On-Windows thing from MS. It seems like they fixed a lot of the frustrating issues recently but it's gonna take a few months for it to get to stable so it's still a non-option for me as well. But i've had extremely good results by using the terminal and "GNU-ish tools" provided by "git for windows" which has worked fantastically. I can interop with the windows system perfectly, I get all my favorite tools like git, cat, sed, grep, awk, all the bash shell stuff, and ssh and more, and it looks a lot nicer than the default cmd. Until the interop with the "host" windows system is better, and they push the fixes to the missing features like inotify and some others, I'm gonna stick with that.

bitcrazed 10y ago
Hey there: PM for Windows Console & Bash here: If you're running Win10 Anniversary Update (AU), know that this was our first formal release of the Windows Subsystem for Linux (WSL) and was, as we made very clear prior to release, missing several key features and capabilities. However, we wanted to get it into users' hands ASAP so that we could asked the community for help to identify what worked and what didn't. And the community leapt to help-out, resulting in literally hundreds of fixes to WSL and to the Windows Console. We've continued to release improvements over the last several months through the Windows Insider builds (release notes: https://msdn.microsoft.com/en-us/commandline/wsl/release_notes https://msdn.microsoft.com/en-us/commandline/wsl/release_not...), and have posted updates and highlights via our blog: https://blogs.msdn.microsoft.com/commandline/ https://blogs.msdn.microsoft.com/commandline/. All these improvements have resulted in Bash/WSL now being very, VERY usable as a real-world dev environment. We've a few more fixes and improvements in the pipe that'll emerge in the next few weeks, but you can feel confident that Bash/WSL is rapidly becoming a viable, highly productive, genuine, Linux compatible environment for running your favorite *NIX-first tools, platforms and technologies. HTH.

pixelcloud 10y ago

Try using Linux with a Windows VM (if required). I have a computer running Arch Linux + Plasma and it is quite nice. With a bit of tweaking you can get a OSX like or Windows like desktop environment. I will use the Windows VM to connect to a VPN and run work applications that require windows, but I can get my email and documents easily through Office365 90% of the time.