@Samuel Gajdoš – thanks for your enthusiasm – as we’ve clearly stated time and again, WSL is not yet anywhere near complete EXPECTGAPS in this initial version. However, know that the team haven’t stopped since shipping Win10AU – in fact, in the first RS2 Insiders build that shipped last wee, several additional improvements to WSL were delivered: https://msdn.microsoft.com/en-us/commandline/wsl/release_notes

Personally the workaround I used with a rails 5 application was to modify the file_watcher config in
development.rb so that it can be disabled with an environment variable.
config.file_watcher = ActiveSupport::EventedFileUpdateChecker unless ENV[‘NO_INOTIFY’]
Then set the the NO_INOTIFY environment variable in my .zshrc. That way one can still easily collaborate
with people not using WSL, or just dev on other machines without Gemfile mess :)
I didn’t need to do anything with the Gemfile at all here, it seemed to fall back to polling nicely.

The suggested workaround will allow you to run the rails server, but it doesn't actually help beyond that. If you try to run your test suite, you'll see the Spring blows up still. I'm glad to see this is on the backlog, and I'd love to hear an update on progress.

Oh come on. I spent whole night and half of the day, sleeping only 3 hours just to update windows/ get bash/ set up everything just to stumble upon this problem at very last step.
Please fix this asap, I was so excited for this, and this was huge letdown.

You can't do web dev nowadays without this stuff. This and inability to communicate with windows processes inside Bash basically means that developers will still use Cygwin/MinGW in the foreseeable future. Looks like you got us excited for nothing.

I just spent a day trying to get our mongo/nodejs/js/react stack working on WindowsBash. I fell into a hole of problems once I got to running mongo and gulp. We need gulp to watch the file system and rebuild sass/jade files as we work on them. Gulp is a major part of our development kit so it needs to work. These tools all work on a mac/linux system and that is the bar we need to meet to make a successful leap to using WindowsBash.

A fantastic job though guys. I am really excited to see this really be used and stop using the emulators and half baked linux commands.