Re:Comparing a web service written in Python and Go [pdf]
by alexchamberlain on Monday October 19, 2015 @08:19AM
(#10412392)
Yet another Go article not fairly comparing technologies. What about a Python implementation that used `asyncio`, for example? What about `PyPy`?
[ Parent
| on HN ]
Re:Comparing a web service written in Python and Go [pdf]
by rbanffy on Monday October 19, 2015 @08:47AM
(#10412499)
It's a Go rewrite of an existing, and probably old, Python application. You are asking them, who already did a rewrite in Go and kindly provided their assessment of the process, to also to a Python rewrite using more modern approaches.
Feel free to rewrite their old Python app in Python for free. They may thank you and even use your port.
Re:Comparing a web service written in Python and Go [pdf]
by laumars on Monday October 19, 2015 @08:46AM
(#10412494)
I think they were just comparing their existing Python deployment infrastructure to a generic Go set up (there are also ways to optimise Go that wasn't explored in that article). It wasn't meant as a "look how much Python sucks compared to Go" type article like a few seem to have taken it. More just disclosing the results of some internal testing they've been doing.
On that note, I would suggest that if you think they could see big gains with little code refactoring simply by switching Python frameworks or even to a different Python runtime, then maybe you should contact them. I'm sure the author would be open to ways to increase their throughput with less developer overhead.
Re:Comparing a web service written in Python and Go [pdf]
by tobz on Monday October 19, 2015 @08:31AM
(#10412438)
Do you have an example in Python of doing fan-out/fan-in? I've done it in Go before, and didn't find it particularly nice to look at (although it did work, and worked well).... so I'm curious what a Python example would look like.