5 ms·
You're right, I see the problem. I'll do an article and post it with detailed analysis. It will take some time because repos are like Tolstoy's quote - "All goo
by systemvoltage 7y ago
You're right, I see the problem. I'll do an article and post it with detailed analysis. It will take some time because repos are like Tolstoy's quote - "All good repos are alike, every broken repo is broken in its own way". There are issues ranging from startup time, upstream packages breaking, constantly changing ecosystem (given for a new language), quirky behaviors and certain problems related to HTTP package and LibPQ packages that I couldn't even debug. So, I rewrote them in Python.
Until then - I concede, please take it with a grain of salt and use your own judgement.
- dnautics 7y agoThanks. I would enjoy reading this too.
- tomkwong 7y agoIt's quite possible that certain area of the Julia ecosystem are not not mature enough. The situation continues to improve quickly as far as I can tell. Rather than rewriting code in Python, we took an approach of using PyCall. It turns out that the overhead of calling Python is very small... at least not to an extent that I had to worry about. For my production system, we used this strategy to access Oracle and Apache Kafka. The code still looks very clean as the calls to the Python packages are just like normal Julia function calls.
- laughinghan 7y agoInteresting, those all sound like serious issues I would very much like to learn more about.
- dklend122 7y agoI'd be interested in reading this as well. In the past legitimate critical blog posts have made a positive impact on the Julia community.
- iamed2 7y agoI can't fault you for switching to something more battle-tested, but did you file issues for the LibPQ.jl issues you encountered? I wrote and maintain the package and we (and others) use it in production so bug reports are much appreciated.