News for hackers. Stuff that matters.
Re:PyParallel: How we removed the GIL and exploited all cores by jnbiche on Saturday June 07, 2014 @07:47PM (#7863485)
Thank you for not asking in a rude and confrontational manner.

No, I don't have any solid data, but I do think the majority of people posting about Go on HN have either Python or Ruby backgrounds. I 've also found a lot of Python people in the Rust community (which I personally prefer vastly to Go).

People need more performance, particularly multicore performance. Traditional Python supporters can put their head in the sand about this if they want, but these highly-performant new languages have clearly found a niche among Python folks tired of trying to optimize all the time.

And yes, there's a fine line between conducting needed optimizations and wasting time prematurely optimizing, but people would clearly rather spend a little more time up front in exchange for a big speedup. The choice is no longer between C and Python -- there's a nice middle ground.

Re:PyParallel: How we removed the GIL and exploited all cores by hcarvalhoalves on Saturday June 07, 2014 @08:38PM (#7863590)
> No, I don't have any solid data, but I do think the majority of people posting about Go on HN have either Python or Ruby backgrounds.

Right. I find it odd because I don't get why Go is a supposed replacement for Python. Does Go have a framework like Django, a good SQL API/ORM, numerical computing packages, scientific packages, machine learning? This is where I see people using Python the most.

> And yes, there's a fine line between conducting needed optimizations and wasting time prematurely optimizing, but people would clearly rather spend a little more time up front in exchange for a big speedup

Yeah, fast by default is not only acceptable but desirable, I don't think using a modern compiled language counts as premature optimization. It doesn't look like using Go is a lot more complex/time consuming than Python, you lose some flexibility but win others (e.g., being able to distribute binaries).

Re:PyParallel: How we removed the GIL and exploited all cores by vertex-four on Sunday June 08, 2014 @08:39AM (#7864526)
Go is vaguely Pythonic (extensive stdlib, and generally adheres to the Zen of Python). Even if there's not much in terms of frameworks, it's great for replacing small parts of a server that have to handle a lot of load. A lot of people have existing Python servers that grew into being performance hotspots. It fits into the sort of niche that node.js does.

Personally, I'm not keen on it - I find that roughly 2/3rds of my code end up being error handling - and hope Rust eventually takes off.

Re:PyParallel: How we removed the GIL and exploited all cores by trentnelson on Saturday June 07, 2014 @07:58PM (#7863508)
> People need more performance, particularly multicore performance. Traditional Python supporters can put their head in the sand about this if they want, but these highly-performant new languages have clearly found a niche among Python folks tired of trying to optimize all the time.

I agree, the status-quo isn't great at the moment if you want to use Python and optimally exploit all your cores. I actually cover that in a more recent presentation: https://speakerdeck.com/trent/parallelism-and-concurrency-wi...