Ditto with plan9/9front and the original Unix.
Now, QT/C++ is the new Motif/C, but not just for Unix, but for doing cross plataform tools everywhere.
I think the future will be shipping static Go binaries with GIO everywhere.
INB4 "disk space", today's compilers and linkers should strip away all cruft from linking by removing any useless library function.
I would like to add a GUI to a little (very little) mysql database updater tool I have in customer hands. GIO is interesting and impressive but I am not as optimistic as you that it will develop into anything big.
Go is not suitable for the kernels etc kind of systems programming, but it's highly suited to the API services kind.
Okay, but it's a pretty reasonable interpretation, right?
"Simpler X, in contrast to Y" makes it sound like Y is a less simple X.
I read this as saying the contrast between go and java is that the former is simpler. The confusion maybe comes about because "simpler" is a comparative adjective (as opposed to, eg, "simple", which is a descriptive adjective), and because there are up to two qualities being contrasted -- simplicity and "being a systems language".
Take it or leave it but I personally was a bit confused by the wording.
It's not "of course" when we're in the middle of conversation about different definitions of "systems".
> You should watch the video if you want Rob Pike's reasoning as to why golang is a systems language
I might do that later, but either way you wrote an ambiguous comment and I don't know why you're lashing out so badly that people try to explain that. Such things happen.
It's funny -- I actually just watched this video yesterday: https://www.youtube.com/watch?v=5kj5ApnhPAE