4 ms·
Maybe they did think it through, but their conclusion reveals some inexperience. It's impractical on many levels. Thus the need for kludgy solutions like blank
by WayneDB 13y ago
Maybe they did think it through, but their conclusion reveals some inexperience.
It's impractical on many levels. Thus the need for kludgy solutions like blank identifiers. I'd rather see a strict mode or some other type of compiler flag.
- jbarham 13y agoMaybe you don't realize that "they" includes Ken Thompson himself... You may disagree with the Go design team's decisions, but it's amusingly absurd to accuse them of inexperience.
- laureny 13y ago> Maybe you don't realize that "they" includes Ken Thompson himself... You may disagree with the Go design team's decisions, but it's amusingly absurd to accuse them of inexperience. Not really, if anything, Go shows that its designers have a lot of inexperience when it comes to modern language design. Go would have been a kille language in the late 90's but it seems to ignore everything that we've learned about language design in the past decade.
- pjmlp 13y agoQuite true, every single feature can be traced back to 80's and 90's languages that for whatever reason did not manage to become mainstream. Maybe one could make a table stating the language feature and which language provided it for the first time.
- pjmlp 13y agoJust an update on my comment. Even if the language is like that, if it helps improving the situation where young developers learn that strong typing does not have anything to do with VMs, I find it quite positive.
- pjmlp 13y agoJust because he created UNIX, does not make him right in every technology decision he takes.
- burntsushi 13y agoImpractical for you. I particularly enjoy the rigidity of the compiler.