Re:Go's power is in emergent behavior
by Iftheshoefits on Saturday April 26, 2014 @09:16PM
(#7653468)
One person's "unplanned patterns that are useful" is another's "this is a potentially dangerous hack that could lead to all manner of headaches in any non-trivial program with even just a few hundred lines of code, let alone thousands or millions."
[ Parent
| on HN ]
Re:Go's power is in emergent behavior
by politician on Saturday April 26, 2014 @09:31PM
(#7653510)
The sweet spot for Go is in the hundreds to a couple of thousand lines of code. Unix philosophy and all that. Leave the monolithic MLOC monstrosities to Java.
Re:Go's power is in emergent behavior
by bsdetector on Saturday April 26, 2014 @11:14PM
(#7653762)
People write MLOC monstrosities in Java because they can. You get some boring financial topic and some sub-par programmers and they'll write as much garbage as the language can possibly sustain.
These things are a testament to how safe and simple Java is as a language.
Not having massive crappy code bases is a negative sign in terms of how reliable and easy to understand a language is.
Re:Go's power is in emergent behavior
by colin_mccabe on Sunday April 27, 2014 @04:02PM
(#7656589)
None of the things you mentioned are "potentially dangerous hacks." Using maps as sets is common in many languages and there's nothing wrong with it. Adding a guard method to an interface is pretty clear and it works well, as well.