Re:Go Python, Go: Stream Processing for Python
by RHSman2 on Thursday October 12, 2017 @03:08PM
(#15460445)
I'll be in touch. Best email please?
Re:Go Python, Go: Stream Processing for Python
by spooneybarger on Thursday October 12, 2017 @04:13PM
(#15460946)
Re:Go Python, Go: Stream Processing for Python
by nurettin on Thursday October 12, 2017 @08:44AM
(#15457540)
So python is the new ruby now.
Re:Go Python, Go: Stream Processing for Python
by coldtea on Thursday October 12, 2017 @08:54AM
(#15457579)
Whatever that even means.
(Besides, Python has been popular longer than Ruby -- which only got big along with Rails' emergence).
Re:Go Python, Go: Stream Processing for Python
by nurettin on Thursday October 12, 2017 @11:35AM
(#15458729)
I'm surprised you could even compare Python's current popularity (obviously due to machine learning libraries) with it's past popularity. Especially with all the comments you've been churning out on HN.
Re:Go Python, Go: Stream Processing for Python
by coldtea on Friday October 13, 2017 @06:41AM
(#15464477)
I've used Python professionally since 1999.
While Python found an extra niche with scientific libraries (and not just/especially machine learning) post numpy and co, it was already very popular then, taking the throne from Perl.
Ruby at the time (and until Rails) was seen as an interesting contester, but nobody doubted Python's top popularity as far as scripting goes.
P.S. What about "the comments I've been churning"? If you mean regarding P3 adoption, then we're still quite a long ways away. Not even 50% -- and well after 10+ years. But that's beside the point. That doesn't mean I don't like Python (including 3).
We are looking for folks to help drive the next version of the API. The first one was done with feedback from a couple of clients who were interested in using Python and in many ways reflects their tastes. Feedback from a wider range of Python users is something we are actively soliciting at this point.
disclosure: I work at Wallaroo Labs, creators of Wallaroo.