Re:Celery, non-blocking code and quest against coroutines
by dang on Thursday June 09, 2016 @12:21PM
(#11870387)
> To all the haters
This is a form of name-calling, which the HN guidelines ask you not to do in arguments. And the "if you can't think of... maybe you shouldn't be" is also a jab. Please don't do these things in HN comments. They add no information, just provocation. Consider how much better your otherwise fine comment would be without them.
Re:Celery, non-blocking code and quest against coroutines
by abotsis on Thursday June 09, 2016 @02:16PM
(#11871234)
The point was to be used as a colloquialism to address people who disagree and encourage them to stop, think and remember everything has tradeoffs and compromises. Then to think about those before simply saying "this isn't a GIL workaround". Maybe it had the opposite effect. :)
I mean, I'm a python fan and this has tradeoffs too (external dependency, task dispatch latency) which doesn't make it suitable every time the GIL gets in the way.
In any case, I don't believe either of these were any more sensational than some of the content in this post.
Re:Celery, non-blocking code and quest against coroutines
by scott_s on Thursday June 09, 2016 @09:45PM
(#11873753)
Returning-in-kind is actively discouraged on HN.
Re:Celery, non-blocking code and quest against coroutines
by ixtli on Thursday June 09, 2016 @12:27PM
(#11870421)
I worry that you would not have posted this response if the top comment had said "Dear dissenters,". However I think you're right about the extraneous and specious "maybe you shouldn't be working in distributed systems" claim.
For example, I wrote a high-speed distributed database load tool, a perfect python use-case. It did some transforms, but nothing heavy. The database (Vertica) could generally keep up. For large files (multiple TB) I'd divide the file into a number of chunks and each interpreter would just seek into an offset, read to EOL, then load until it reached the next interpreter's offset. I built it in a few hours.
Just trying to say that there are very few real-world workloads (were python is extremely useful) that the GIL really gets in the way. It certainly doesn't offset the time and ease of developing a solution.