News for hackers. Stuff that matters.
Re:Go’s runtime C to Go rewrite, by the numbers by Lewisham on Monday September 01, 2014 @03:24AM (#8251838)
I would guess it is the `if err` lines and other such gofmt artifacts that expand the LOC. Go is higher-level, but it's not terse. It's deliberately pretty explicit. IMHO 100 lines of Go might well do the same as 100 lines of C, but the Go will be much more readable code.
Re:Go’s runtime C to Go rewrite, by the numbers by seanmcdirmid on Monday September 01, 2014 @03:26AM (#8251844)
That is easy to check, could the author put 100 lines of C code next to 100 lines of equivalent Go code and let us judge for ourselves?
Re:Go’s runtime C to Go rewrite, by the numbers by sambeau on Monday September 01, 2014 @06:02AM (#8252181)
If we judge for ourselves we will only be checking our opinion.

Could you provide a readability algorithm in some form of executable that we can run against the 100 lines of c and Go code — then we'll be able to judge correctly.

Re:Go’s runtime C to Go rewrite, by the numbers by pjc50 on Monday September 01, 2014 @08:34AM (#8252523)
readability algorithm

Sure, it's next to the objective poetry quality metric.

"Shall I compare thee to a summer's day?"

> TYPE ERROR

Re:Go’s runtime C to Go rewrite, by the numbers by seanmcdirmid on Monday September 01, 2014 @06:14AM (#8252211)
Honestly, I just want to see them side by side. We can then debate our subjective interpretations vs. debating pure biases.