Re:Where are we in the Python 3 transition?
by jacquesm on Friday January 01, 2016 @06:33PM
(#10824090)
Agreed on the library part, that's my biggest hang-up in making more (and faster) progress with Erlang projects. Sometimes I even end up rolling my own and coming from languages with substantial 'batteries included' library systems this is a real drawback.
On the other hand, when it finally works it is absolutely bullet proof and that's a feeling I have with very few other languages and eco systems.
The degree of isolation between subsystems and the reliability are absolutely un-matched. Neither is the learning curve :(
Re:Where are we in the Python 3 transition?
by BuckRogers on Saturday January 02, 2016 @02:02AM
(#10825382)
Have you tried Elixir? If so, just wondering if you found the learning curve to be as difficult as Erlang.
Take a look at the PyPI stats for Python3 packages vs. the Hex stats for Erlang packages:
https://python3wos.appspot.com/
https://hex.pm/
The vast majority of common packages are compatible with Python3. Moreover, a common Python package gets about 100x the downloads of a common Erlang package. Even with only 20% of Python users on Python3, that's still about 20x the users that Erlang has.
Python3 adoption only sucks compared to the installed base of Python2. Compared to any niche language - Haskell, Erlang, Rust, Swift - it's massive, and you're much more likely to find a battle-tested library in Python3 than in your niche language.
(The bulk of my work is actually in Node and Swift these days. Node has a mammoth package library, but that's because its culture encourages many small modules and lots of code re-use. In my experience, I've found that the chance of finding a robust, well-supported Node module is roughly equal to the chance of finding a robust, well-supported Python2 library, and is maybe 20-30% greater than the chance of finding a robust, well-supported Python3 library. The Swift library situation is much, much worse than Python3.)