3 ms·
I think that's an accurate distillation of what was said. Am I supposed to infer some opinion from you on that? I'm not sure if you were just summarizing or h
by kbenson 13y ago
I think that's an accurate distillation of what was said.
Am I supposed to infer some opinion from you on that? I'm not sure if you were just summarizing or have a fundamental disagreement with the stance, which you thought would be self evident.
- randall 13y agoI think he's saying the OP is being contradictory. "I don't mean to boast, but I'm awesome" would be a similar statement. Trying to defeat criticism by deflecting the critique at the root, while actually fulfilling said critique is a common argumentative tactic that, while noble in its attempts to avoid offense, is intellectually dishonest.
- kbenson 13y agoThat only follows if you think that a language being made for "people of a certain level of intelligence" is a negative assessment (even if I find the wording crude). I don't think that, because I don't think it precludes "more intelligent" people from getting good use out of it. The designers are not omniscient, and their desires mean nothing in the real world, beyond how the product of their will is actually used. All that's just a long winded way of saying that who it's made for and who finds good use out of it are not entirely equivalent. As such the tptacek's statement seemed very neutral to me.
- jbooth 13y agoI think his fundamental disagreement is with the idea that embracing simplicity makes one a simpleton. I'm primarily a Java and Go coder and think that writing boring code to solve difficult problems requires much more intelligence and artistry than writing complicated code.
- Kurtz79 13y agoYes. IMHO a smart programmer does not use a complex or a language "by smart people for smart people" because "he can". He will use the best language for the problem/domain at hand. Even if OP is right and GO is a "simpler" language than others, if it allows to solve a range of problems without the added mental load required by, say, C++ why should't he use it ?
- bdamm 13y agoLet me extend your axiom a little bit... Since sharing source code with as wide an audience of programmers as possible will almost always bring increased value to your system, then using a language that can be widely understood and modified safely makes it the best language for the problem/domain at hand.
- nahreally 13y agoErgo, Javascript.
- kbenson 13y agoI think his fundamental disagreement is with the idea that embracing simplicity makes one a simpleton. I can agree with that. I also believe that using a simple tool does not presuppose simple outcomes. To me the rewording looked like a fairly neutral assessment of a few language features. What I was fishing for was if there was some positive of negative opinion behind them and what it was driven by. Without that the comment seemed fairly useless, and I'm fairly sure tptacek's not shy about sharing his opinion. ;)
- cgag 13y agoI think it's that Go embraces familiarity more than simplicity.
- papsosouid 13y ago>I'm primarily a Java and Go coder and think that writing boring code to solve difficult problems requires much more intelligence and artistry than writing complicated code. That is a false dichotomy, and a particularly dishonest one at that. The options are not write complicated code in a modern language vs write boring code in an obsolete language. Go is bad because it gives the programmer poor tools to write any kind of code to solve difficult problems, boring or otherwise. Basic simple functionality that has been established for decades is being ignored because people insist on pretending that having a good language is somehow a problem and makes code complicated.