3 ms·
So my main concern was being able to easily run elixir/erlang, with some flavor of unix as a production target. Therefore running natively on windows was, at b
by fcbrooklyn 8y ago
So my main concern was being able to easily run elixir/erlang, with some flavor of unix as a production target. Therefore running natively on windows was, at best, a nice to have. On OSX I could just work in the native environment, since it's unix, albeit a bit of a peculiar unix with the occasion random odd thing installed to trick me. On windows I've found two possible solutions so far. The first is Ubuntu installed under WSL. I've heard people complain that WSL doesn't always work, but so far I've had no issues. easily installed elixir, erlang, npm and vim. Phoenix works no problem. I installed elixir natively on windows as well, just to see if I could, and again, no problems at all, and it works fine. I'm using cmder, which gives you a much more unix-like command environment. Chocolatey is the equivalent of homebrew, and actually seems to be superior, or at least more complete. ("choco install chrome", "choco install spotify", kinda handy). I'm mostly a vim guy, but I'm not religious about that. Neovim worked fine in WSL, so that's all good for now. Might give vscode a shot, as it has some nice elixir plugins.
Finally, I installed vagrant under windows, with virtualbox. I haven't used that before, but I think it could provide another alternative dev environment in case WSL turns out to be unreliable. My ultimate fallback plan was always to use vmware or similar and just run unix for dev, windows for things like excel, but my feeling is I'm not going to have to do that.