News for hackers. Stuff that matters.
Re:How we rolled out one of the largest Python 3 migrations by crdoconnor on Tuesday September 25, 2018 @04:42PM (#18070304)
Go code is about ~30% more verbose than equivalent python.
Re:How we rolled out one of the largest Python 3 migrations by melling on Tuesday September 25, 2018 @06:10PM (#18070970)
How much faster is Go? Memory usage?

It has to be less demanding on your laptop battery, for example.

Re:How we rolled out one of the largest Python 3 migrations by oofabz on Tuesday September 25, 2018 @10:19PM (#18072186)
Performance depends very much on what you are doing. Native Python code is much slower than Go, but Python code execution is not the bottleneck in many Python programs. NumPy may be faster than Go and disk IO is the same speed in each.
Re:How we rolled out one of the largest Python 3 migrations by BuckRogers on Wednesday September 26, 2018 @01:19AM (#18072967)
Go performance would be next tier from Python but memory usage a little less so. The Go team has made great strides in that regard from what it was. The runtime is always getting better, and it's fun to watch.

Rust or native platform (Swift/C# .Net Native, depending) are going to be even more ideal for battery usage.

Proper algorithmic choices are even more important and paramount no matter what is used. It goes without saying that poorly implemented Rust can be bested by well implemented Python.

Re:How we rolled out one of the largest Python 3 migrations by azhenley on Tuesday September 25, 2018 @05:37PM (#18070715)
Wow, I wouldn't have expected that. Do you have a reference for the 30%? I'd like to see what is going on to cause that big of a difference.
Re:How we rolled out one of the largest Python 3 migrations by SEJeff on Tuesday September 25, 2018 @05:42PM (#18070751)
Every other 5 lines being the equiv of:

    if err != nil {
        ... error handling ...
    }
Python just uses exceptions, and they bubble up. No need for this excessively verbose error checking.
Re:How we rolled out one of the largest Python 3 migrations by SEJeff on Tuesday September 25, 2018 @05:55PM (#18070842)
I'm not sure why it is downvoted. This is true. I write both Golang and Python as part of my day job. I love both languages, but this is definitely the truth.

Go is more verbose. It also gives you the wonder of the compiler telling you about doing stupid things. That doesn't make it a worse language.

Re:How we rolled out one of the largest Python 3 migrations by samfisher83 on Tuesday September 25, 2018 @06:42PM (#18071170)
Does go not have exception handling?
Re:How we rolled out one of the largest Python 3 migrations by SEJeff on Wednesday September 26, 2018 @11:03AM (#18076642)
Go does not have exception handling at all. It is a proposal they're seriously considering for go2:

https://go.googlesource.com/proposal/+/master/design/go2draf...

See the bits about error handling and error values.

Re:How we rolled out one of the largest Python 3 migrations by samfisher83 on Thursday September 27, 2018 @10:15AM (#18084655)
What was the reason the go designers didn't have exception handling?
Re:How we rolled out one of the largest Python 3 migrations by SEJeff on Thursday September 27, 2018 @11:53PM (#18090919)
Read Rob Pike's post on why: https://commandcenter.blogspot.com/2012/06/less-is-exponenti...

The go2 proposal shows that in this respect, he was woefully wrong.

Re:How we rolled out one of the largest Python 3 migrations by lacksconfidence on Tuesday September 25, 2018 @06:56PM (#18071255)
go has something in the same general area of error handling called panic/recover. It's not exceptions in the normal sense, and devs expect nothing should panic across api boundaries.