vereis / jarlang Goto Github PK

Currently, Jarlang is strictly only compatible with Unix-like systems due to certain things such as Erlpkg using bashism internally.

I'd wager there are a few things we're doing in Jarlang itself which are unix-only too, but I'm unsure about that.

We should look over our code and produce an alternative build method for compiling the project for Windows development natively, or at least make the build compatible with Cygwin.

Directly building on Windows is probably a better idea however, because there is no Cygwin build of Erlang for several very good reasons which are outlined here: http://erlang.org/doc/installation_guide/INSTALL-WIN32.html

I don't believe it would be too hard to do and would be a good thing to do eventually, especially before the project gets much larger.

Currently, Jarlang asynchronously compiles by default in two places:

1. We spawn new async processes which transpile individual files passed into Jarlang
2. Each of these async processes spawn N async processes handler the transpilation of each individual function in said file.

While this hasn't caused any issues in testing, for development, the error messages become much less readable if an error is thrown in a process other than the main process.

Also, I'd wager that blindly spawning so many processes wastes more resources than saves since some function transpilations will be completely trivial such that the time it takes to spawn the process is much larger - we need to benchmark this.