> I find this statement highly surprising.. wander if you meant to reverse > this.. My quant friend who had worked for years in Python had trouble > parallelizing Python code (may be resolved now..). I'm not familiar with R, > but Python has the GIL and associated problems. I also thought Erlang was > best-in-class (for concurrent, not "parallel"). >
Oops, you are right, it's exactly the opposite. Consider it a result of quick answer between 2 meetings. Julia's capabilities are much better for concurrent and parallel programming than these in Python or R. For those in the Java/Scala world, I'm less sure about reusing that, I know > you can with JavaCall.jl, but understand there are bugs and limitations to > it. Unfortunately, that's true. @aviks has made a great work connecting Julia to JVMs via Java Native Interface, but as far as I can see, JNI is shitty by itself, and it's very hard to to make integration between Julia and Java really stable. "HttpServer.jl, has low latency 0.5 ms and high throughput (latency on the > same order of Python's Flask and Scala's Spray mature frameworks, and > throughput also comparable[82])." That's funny, because specified reference leads to an issue on performance that was opened by me and incorrectly interpreted by the author of Wikipedia page. At that test Julia outperformed Flask, but was still 3-6 times slower than Spray. Seems like I need to repeat my tests to get latest results. I didn't check if this works the same, or just similarly? They have totally different APIs and approaches in general. The main point is that if you want to keep it working with updated version of Julia and libraries, you have to adapt web application too. And it's really not funny to come back to a code written half a year ago just because libraries it used are now deprecated. Wouldn't that be kind of trivial, since Julia already acts as a web server, > to load files from disk and forward? To tell the truth, I have no idea. I know that for each static file (e.g. image or CSS) there's a specific MIME type, specific headers, etc. There is probably some caching policy and specific way to write bytes to a socket. But I don't know for sure and just want to provide web interface to my code, doing it as simple as possible. (please, don't consider it as a criticism of Julia web stack - I'm really thankful to all the people involved and pretty impressed by the work they've done - but rather as a TODO list for future development).
