Re:The ups of downs of porting 50k lines of C++ to Go
by cgag on Saturday March 07, 2015 @02:13PM
(#9162745)
I think some of those "Go lacks feature X" are the arguments you're eager to hear, and not simply invalid. Go lacking generics but having generic map/array types built in is an example of going against the Scheme school of thought. They're not built up from primitive features, but handed down as language features.
I think this post makes those criticisms well: https://www.quora.com/Do-you-feel-that-golang-is-ugly/answer...
Re:The ups of downs of porting 50k lines of C++ to Go
by Solarsail on Sunday March 08, 2015 @06:12AM
(#9165188)
In addition to those, there is Iota. Which is completely special-cased syntax sugar, which is not reusable outside of a single context. You can't use it at all more generally, and get potentially non-obvious code from using plain integers silently.
Re:The ups of downs of porting 50k lines of C++ to Go
by Someone on Saturday March 07, 2015 @03:00PM
(#9162911)
> Ask yourself. Which of these two languages are more likely to be complemented by language nerds/snobs - C++, or Scheme...
I don't understand this question.
I think the OP means complimented (aka praised), not complemented (aka enhanced)
We are advocating the same school of thought. However languages designed by such schools rarely get mainstream - Scheme, Lua, Smalltalk, to name a few that I know of. People acknowledge them, put them on the altar and ignore them. Go is the first language in decades I know of that boasts simplicity as a feature and gets mainstream; C is the last one before Go. There are things I dislike about Go (esp. lack of generics), but I find it worth defending. I apologize for my somewhat cynical intonation, if that caused confusions.
> Ask yourself. Which of these two languages are more likely to be complemented by language nerds/snobs - C++, or Scheme...
I don't understand this question.
> And some people who apparently belong to this school of thought are criticizing Go for not being orthogonal enough.
I am very eager to hear such criticisms, but I haven't come across any of them. Most "criticisms" on Go are simply "Go lacks feature X", which are simply invalid. A valid criticism is "It is very tricky for me to solve problem X with Go, and adding feature Y will make things easier", but I don't always buy it unless the author is smart enough to convince me that the difficulty lies in the limitation of Go instead of the author's intelligence.