Sorry @gregvaughn I just saw your note.
I do development work with Elixir on Windows all the time. I can’t say that I’m doing production code but I’m not writing production code anywhere anyway.
Everything works on Windows–even without the Bash support. There was a conversation over on Slack about one thing not working under the Bash shell on Windows (which is called WSL) but apparently with a later rc build that was fixed.
I use emacs on Windows (not an issue at all) but there are several good editors on Windows with language bindings for Elixir. Using emacs with alchemist I can write my code and test it without an issue.
The main problem I’ve run into is not an Elixir issue–it’s an Erlang issue. The Erlang installer, quite correctly, follows the Windows convention of putting it’s binaries under “Program Files\erl” The space in that directory name (which is a sure sign that most of the MS Windows developers know squat about CLI’s) causes no end of problems. I know, I know–just surround it with double quotes. But then you run into issues if you need double quotes in other places on the command line.
The other main drawback of Windows is support for compilation of libraries. For example, ComeOnIn needs to compile some NIF’s for its library. This can be done with a little bit of effort but it’s nowhere near as smooth as it is with a Linux box. But if you don’t need NIF’s then it’s not a big concern.
Basically I’d say that Windows isn’t a bad place to develop Elixir apps–it’s just not as nice as LInux; even with WSL (which by the way isn’t GA just yet) it’s still a bit clumsy.
