|
|
|
|
|
by heroprotagonist
3581 days ago
|
|
Well, you are free to address it if it bothers you. The typical response to this of _I don't want to_ or _I shouldn't have to_ seems a bit naive when working with open source projects. The issue has only been on the tracker for two weeks, and it has the 'HelpWanted' tag, so it's not like they're opposed to improving the speed here. If you're going to throw out specific numbers, you should probably get them, or at least the ratios, correct. Numbers from the tracker are: Go: avg 1.489 secs
Python: avg 0.933 secs If you'd like to test this on a really large dataset to come up with how long it would take for Python to perform the same operation when Go requires 5 hours, that might be a bit more useful. If we just look at the available data, then the _extrapolation_ for Python would not be 2.5 hours. There's still a gap, but there's no need to exaggerate. |
|