One of the main purposes of go is that there are too many big things inside G, and the system-level development of mega projects is very painful, and go positioning replaces C++,go to win simply (KISS)

In the past, in order to do compiler, study + realized almost all kinds of languages. Now reading the grammar Handbook is almost quick to understand the content of the entire language. Then I contrasted go and rust and found that the go type system was just a piece of patchwork. This leads to the same language as C, which requires great skill to write large programs. Rust does not have this problem, and the composition of each part is very harmonious.
----------------------------------------------------------------------

Rust is excellent, and the function is inherently more elegant than the command-style. But at the same time, we must also see that the two languages are positioned differently. Go is positioned to replace C (or C + +) as the basis for all software. and Rust wants to be an epoch-making language, and if successful, it will be subversive.

But it should also be seen that
Go's goal is simple, now also relatively stable, can use the
While Rust is strong, it is still at an early stage, and everything remains to be developed.

If rust can achieve most of its features, it will be a very good language to look forward to.

----------------------------------------------------------------------

The struggle for language is time-consuming, and there is no need to talk to these people. Everyone has their own preferences, some people on the Java call, some people do not like go, you say nothing is useless. I woke up with my own comfort.
By the way, I would like to remind you that there is no reason to say that some compiler danale can judge. First is not Danale, much danale another said if you ask Rob
Pike, he must say that go is better than rust, Rob and this person is more danale than who? Linus said C + + sucks, difficult to C + + programmers all-in-trade?

Self-absorbed in doing their own things is.
As for the phrase "the author actually said that the time to learn C + + and go to write 64 open source projects as much time", hehe, he obviously did not read this joke.

Are you? Go team of people inside, application development of Danale actually still a lot of
one of the main purposes of go is that there are too many big things inside G, the system-level development of mega projects is very painful , so it is estimated that go development and different team have communication, the address of the problem is a lot of giant development team in the actual problem. For example, the interface of Go is designed for large-scale applications, because everyone knows it. Go's advantages in the actual large-scale application projects have been reflected, and not to say that except Google no one use, the use of the people feedback is what, we estimate also heard

The Dart team starts out differently because JavaScript is so ... That's it. But Dart is always the main front-end bar. The two basic can not compare.

I use go not because Ken Thompson, Rob Pike These people, I think C + + sucks is not because of Linus. That's what I liked or didn't like after I used it.
Don't be superstitious about authority. The best way to persuade someone to go is not to pull out a bunch of celebrities, but to do a great project and library to get people to take the initiative
----------------------------------------------------------------------

This, the GUI library is obviously not within the Go Team development schedule. I think that using swig as a binding for other GUI libraries (such as QT) is a better pattern than pyqt .
----------------------------------------------------------------------

Now I've been focusing on the GO language for a long time, feeling that the authors are very tightly controlled and that many good suggestions have been rejected, see Golang-nuts Mail Group. Some advice, they only need to do very little work, can have a good effect, they just refuse to improve.
----------------------------------------------------------------------
Like what? I guess you mean ' #! '. Do you?
I think it's good to be more strict in control. Because adding a feature is simple, it is difficult to remove an existing feature from the language.

If an attribute can be implemented externally (for example, with Gorun implementation #!), then there is no need to increase the complexity of the language itself.
So not go team lazy, even some very simple implementation of the recommendations are not adopted (#!) or refuse to improve.

I think go is a simple, consistent (orthogonal) win. This is consistent with the Unix-bound software style, in other words the kiss principle.

----------------------------------------------------------------------
Reference: Https://groups.google.com/forum/#!topic/golang-china/aX61jyZXBws%5B1-25-false%5D

One of the main purposes of go is that there are too many big things inside G, and the system-level development of mega projects is very painful, and go positioning replaces C++,go to win simply (KISS)