The Value in Go’s Simplicity

Re:The Value in Go’s Simplicity by tensor on Saturday November 16, 2019 @03:56PM (#21554894)

This philosophy is about as far from what I value as it's possible to get. An easily understandable program that doesn't solve the problem is worth absolutely nothing. In fact, if it's code someone is depending on it's probably worse than no code at all. In some applications it could even cost people their lives.

Correctness is a basic starting point. It's the minimum viable offering.

[ Parent | on HN ]

Re:The Value in Go’s Simplicity by BurningFrog on Saturday November 16, 2019 @11:28PM (#21556564)

That's the most common opinion, and the one I used to hold.

Here is my counter argument.

Readable code that has some bugs is fixable. Because you can understand what it's doing and how to change it.

Working code that is unreadable is basically dead. No one can make changes to code they don't comprehend. The only thing it's good for is running it as is, much like a compiled binary.

[ Parent | on HN ]

Re:The Value in Go’s Simplicity by acheron9383 on Saturday November 16, 2019 @04:51PM (#21555214)

That old adage, the best code is the code not written. Programs have to solve a problem to be worth anything.

[ Parent | on HN ]