News for hackers. Stuff that matters.
Re:John Carmack on Inlined Code (2014) by artursapek on Tuesday July 19, 2016 @09:50AM (#12121730)
> it made fixing any minor bug take weeks.

My god.

A lot of these fancy language features sound good on paper but can be so abused that even just coming to understand the code takes up too much space in your head.

https://twitter.com/davidcrawshaw/status/507268175256231936

Re:John Carmack on Inlined Code (2014) by MyNameIsFred on Tuesday July 19, 2016 @10:33AM (#12121990)
Emphasis belongs on abused. Interfaces are swell. Subclasses of classes which implement an Interface are swell too, when they extend simply by altering the way said interface is achieved. When you subclass to "add more stuff", however, you get the kind of nonsense described.
Re:John Carmack on Inlined Code (2014) by deong on Tuesday July 19, 2016 @04:28PM (#12124635)
The problem, in my opinion, is that the Java community (generalizing, I know) decided to bless that abuse as a best practice.
Re:John Carmack on Inlined Code (2014) by donatj on Tuesday July 19, 2016 @10:06AM (#12121833)
This is part of why I am so in love with Go. I have never read Go I couldn't understand. It's very clear at heart. I have read through much of the standard library and it all makes sense.
Re:John Carmack on Inlined Code (2014) by MyNameIsFred on Tuesday July 19, 2016 @10:35AM (#12122010)
Do you think that's that's because the language inherently makes things readable, or is it simply because the language is too new to have popular anti-patterns?
Re:John Carmack on Inlined Code (2014) by mixedCase on Tuesday July 19, 2016 @11:55AM (#12122450)
The simplicity of the language and some of its choices really force you to do things a certain way that comes out almost universally legible instead of going with what may feel easier or "clever" to write. This is why it's so widely criticized (which doesn't mean that some of its criticism isn't fair).

Also gofmt having the last word on what code is acceptable and what isn't helps kill a lot of arguments that aren't worth having.

Re:John Carmack on Inlined Code (2014) by stcredzero on Tuesday July 19, 2016 @12:49PM (#12122853)
In a way, it's like the Go team chose to write something that has some of the coder UX of Smalltalk, but in a C-like statically compiled language. There is a useful region of language design space around the "simple language" concept, and they seem to be making the most of that particular design space maxima.
Re:John Carmack on Inlined Code (2014) by agumonkey on Tuesday July 19, 2016 @05:01PM (#12124861)
The team promotes heavily dead simple code over PL abstractions. Taken from some golang con slides where they said there would be nothing new in go, only perf and bug removal for a while.
Re:John Carmack on Inlined Code (2014) by donatj on Tuesday July 19, 2016 @12:28PM (#12122666)
It's an active choice of the language to not allow many syntactic sugars that make the code have a much higher learning curve.

https://www.youtube.com/watch?v=rFejpH_tAHM is a good overview.

Re:John Carmack on Inlined Code (2014) by jasonm23 on Tuesday July 19, 2016 @10:16PM (#12126420)
In many ways I'm terrified by Java programmers who have never heard of pattern abuse.