51–60 of 189 posts
It's really annoying to have to log in to read something on google+, or groups for that matter. I just won't do it.
This happens only if you have some Google login cookies already -- if you delete all your Google cookies then you won't be asked to log in.
Earlier quoted context omitted.
In hindsight it doesn't seem so surprising. Go really isn't a good alternative to C++ for the kinds of things that really need the low-level control and direct memory access C++ provides. And if you don't really need those things you probably should have moved on to Java or Ruby/Python/etc already. And since a lot of Java shops are fantastically risk averse I'm not at all surprised that the same kind of people that w…
Straight from Rob Pike -- http://commandcenter.blogspot.com/2012/06/less-is-exponentia... Python and Ruby programmers come to Go because they don't have to surrender much expressiveness, but gain performance and get to play with concurrency. C++ programmers don't come to Go because they have fought hard to gain exquisite control of their programming domain, and don't want to surrender any of it. To them, software isn…
I call BS. The parent explanation is much better: for a lot of the kinds of jobs C++ is good for, Go is not that good, whereas for a lot of things Python is good for, Go is as good and has better performance.
Earlier quoted context omitted.
You have to login? It doesn't do that for me, and I'm not logged into any Google products...
Google has invented a new login state between "logged in" and "not logged in" called "not logged in enough". It's kind of like being logged in, except nothing works and you get asked to login again. Also, you can't logout.
Creator of SASS and Haml now using Go for whole production system. When asked about surprising things about Go, its creators have said that they expected to recruit people from c++ communities, instead it seems to be more ruby/python people.
I think a lot of it is that people sort of did want some static type checking, but were not willing to give up on things like garbage collection or some of the other niceties that the dynamic languages provided. As someone who has been clamoring for a statically-checked Python-esque language, Go looks awesome.
Creator of SASS and Haml now using Go for whole production system. When asked about surprising things about Go, its creators have said that they expected to recruit people from c++ communities, instead it seems to be more ruby/python people.
I think that Mozilla's Rust is aiming squarely at C++ developers, whereas Go is more of a Java replacement. And it's interesting to see Python and Ruby being squeezed lately, from various directions; Clojure, Go, other languages. Since Python went mainstream and started being picked up for serious projects, it naturally came under the spotlight a lot more than it had previously, and I think many people have started t…
Well, it does excel in scientific computing. Biologists, astronomers and such use it a lot, and it has lots of advanced math/stats/physics etc libs, with fast C implementations underneath.
How's the garbage collector these days for Go? Is it close to the performance of the Java GC?
"100% of our production system is now running Go as 95% of our application (C being the other bits)" So... 95% of their production system is running Go.
the C code is also being run under Go's control via Cgo.
Earlier quoted context omitted.
I meant "what functionality is the remaining 5%." Not "what language is it." Basically, once you are 95% Go, what parts are hard to convert to Go to make it 100%
Probably binding to pre-existing C libs. It will take some time to replace 40 years of existing accumulated C libraries.
How's the garbage collector these days for Go? Is it close to the performance of the Java GC?