News for hackers. Stuff that matters.
Re:Space Monkey dumps Python for Go by hyp0 on Tuesday April 22, 2014 @01:38PM (#7629108)
I thought you had meant that Go was "easier to maintain" than python - most of these don't apply to Python: Python has faster compilation times (0); interfaces without recompiling; formatting conventions; and numeric conversions is compared explicitly with C. Channels is the only one that applies to python.
Re:Space Monkey dumps Python for Go by TylerE on Tuesday April 22, 2014 @02:04PM (#7629271)
As some who generally prefers Python to Go quite strongly, the formatting situation is no where NEAR equivalent. With go it's trivial to setup your editor to perfectly reformat every time you save, or even on carriage return, and it does in a way that is 100% consistent and will never alter the logic of your code.
Re:Space Monkey dumps Python for Go by sergiosgc on Wednesday April 23, 2014 @05:36AM (#7633009)
I'm not a python expert by any measure, but I've written a couple small projects with it. Python surprises for how well documented it is. In this specific case, PEP8 lays down most formatting conventions, so you'd expect some tooling to be available. Is this not the case?

A quick Google search brought up this, for instance:https://bitbucket.org/StephaneBunel/pythonpep8autoformat

Re:Space Monkey dumps Python for Go by NateDad on Wednesday April 23, 2014 @08:13AM (#7633439)
The thing is, while this kind of thing is available for pretty much every language, it is standard for Go. As in, if you don't gofmt your code, everyone who looks at it will bug you to format it. That's a huge difference. There's basically zero code in the wild that you'd ever want to use that /isn't/ gofmted.
Re:Space Monkey dumps Python for Go by kyrra on Wednesday April 23, 2014 @11:20AM (#7634498)
Exactly the point. Go is a VERY opinionated language. You see the term "idiomatic Go" used very regularly. The Go team and community push hard for everyone to follow a set way of doing things. This means all Go code must be formatted a certain way, handle errors in a certain way, etc. People even put pre-commit hooks into their VCS system that will reject .go commits unless they are properly formatted before commit.
Re:Space Monkey dumps Python for Go by yawboakye on Wednesday April 23, 2014 @06:51PM (#7637445)
I use Vim and there's a plugin just for that: making sure my code is PEP8 compliant.
Re:Space Monkey dumps Python for Go by rakoo on Tuesday April 22, 2014 @02:02PM (#7629261)
Maybe he meant that having a typed language that is checked at compilation time is a huge plus for maintenance, and the usual downsides that come with compilation (mainly slowness) are pretty much inexistant with Go.
Re:Space Monkey dumps Python for Go by est on Tuesday April 22, 2014 @09:26PM (#7631534)
I think he mean one single big ass executable is way easier to maintain than pip install & virtualenv everywhere.

Yes we can also make a single big ass executable out of any python code but it's slower and not supported out of the box.

Re:Space Monkey dumps Python for Go by crag on Tuesday April 22, 2014 @11:36PM (#7631942)
And IMHO that's whats killing python - the fragmentation.
Re:Space Monkey dumps Python for Go by dekhn on Wednesday April 23, 2014 @11:22AM (#7634521)
You are incorrect about compile times in many ways. First- python byte compiles to a weird VM. Then it executes that. Second- go compilation times are comparable to python byte compilation time but the result is a native executable.
Re:Space Monkey dumps Python for Go by spoiler on Tuesday April 22, 2014 @04:23PM (#7630180)
Python is interpreted, not compiled... Of course it has 0 compile time.