Guys slightly off topic, but please do keep the colorblind people in mind. The colors used for the graphs are so similar that I can not differentiate them.
Official Go support
31–40 of 117 posts
Re: Official Go support
#32Guys slightly off topic, but please do keep the colorblind people in mind. The colors used for the graphs are so similar that I can not differentiate them.
Re: Official Go support
#33Earlier quoted context omitted.
Go's JSON parser ignores fields that aren't present in the destination type, so the addition of new parameters shouldn't be a problem.
I believe the issue is that new parameters wouldn't be accessible without a library update.
My sense is that the Go developer culture is a lot more open to frequently updating their dependencies than the Java developer culture. Fetching dependencies from git is built into Go, after all.
Re: Official Go support
#34Re: Official Go support
#35Guys slightly off topic, but please do keep the colorblind people in mind. The colors used for the graphs are so similar that I can not differentiate them.
Interesting - I thought it'd be red/green, but it's blue/purple (which I thought were colors chosen for the color blind).
Is blue/purple color blind less common? Can you differentiate between red/green?
Re: Official Go support
#36Guys slightly off topic, but please do keep the colorblind people in mind. The colors used for the graphs are so similar that I can not differentiate them.
Interesting - I thought it'd be red/green, but it's blue/purple (which I thought were colors chosen for the color blind). Is blue/purple color blind less common? Can you differentiate between red/green?
If you're red-deficient, then purple/blue is also a bad choice for colors because you can't see the red components of purple.
Re: Official Go support
#37Can someone explain? I'm a big fan of C and python and I've never used Go. My initial impressions from readings were that Go is a better C. But then I came across a Go person who was lamenting that misunderstanding and that Go is python but with better performance. What's it all about? Also even if we compare it to C I don't like the garbage-collection thing at system level. Also what does Go let you do in terms of g…
Go was originally pitched as a better C, but it seems to be finding a niche as a better Python or possibly a better Java. Go binaries have built-in GC, and Go will probably never reach C levels of performance. There is a lot to like about Go and it is working out very well for a lot of people, but it isn't appropriate for every situation. If you want a better C, better to look into Rust: http://www.rust-lang.org/
When Google will completely deprecate Java for Go on Android (could be a number of years, if ever), then Java should imminently become irrelevant (over a number of years, maybe a decade, or maybe it will never disappear completely, but the point is it will rapidly decline with new and existing developers).
Re: Official Go support
#38[deleted]
Re: Official Go support
#39Can someone explain? I'm a big fan of C and python and I've never used Go. My initial impressions from readings were that Go is a better C. But then I came across a Go person who was lamenting that misunderstanding and that Go is python but with better performance. What's it all about? Also even if we compare it to C I don't like the garbage-collection thing at system level. Also what does Go let you do in terms of g…
Go's syntax and semantics seem ad-hoc, hard to remember, and inconsistent, but that's because Go was designed from uses cases and experience by prominent thought leaders such as Rob Pike and Ken Thompson, and Google. For example, sometimes you'll get Unicode code points, but sometimes you'll get bytes of UTF-8. The language was designed to give you the right one in the right case. UTF-8 is coupled with the language because it's the most useful choice. Another example is that pointers are automatically dereferenced, but not when you have pointers to pointers, because that's less useful. If any thread runs in an infinite loop that doesn't call built in functions, the entire runtime will freeze. But this is by design. You're meant to do actual useful stuff in your loop such as calling IO functions (which will yield to the scheduler) or calling GOSCHED.
It was designed to compile fast, and compiles faster than most languages and still has near C-speed. It doesn't have a GIL so it has better concurrency (Java style memory model). It has no complicated features like generics, instead you just use type assertions when you need. It also has impeccable tooling.
Re: Official Go support
#40Can someone explain? I'm a big fan of C and python and I've never used Go. My initial impressions from readings were that Go is a better C. But then I came across a Go person who was lamenting that misunderstanding and that Go is python but with better performance. What's it all about? Also even if we compare it to C I don't like the garbage-collection thing at system level. Also what does Go let you do in terms of g…
Go is a very pleasant language to develop software products in. Unlike the dynamically typed languages, it doesn't trade speed for beauty of syntax. This means that sometimes syntax can be a little non-uniform, but there's always a reason. Unlike C and C++, it doesn't trade safety for speed of execution. There are no buffer overflow vulnerabilities in Go applications. It treads a fine line of where to let the languag…
> There are no buffer overflow vulnerabilities in Go applications
Actually there are in certain cases [1], but there's a good reason for that.
1. http://stackoverflow.com/questions/25628920/slicing-operatio...