OpenCensus is not a vendor specific project. The data OpenCensus collects can be exportable to any tracing backend. We already have a Jaeger exporter for Go: https://godoc.org/go.opencensus.io/exporter/jaeger.
Code instrumented with OpenCensus can export to any backend by changing the registered backend.
LLVM is a future consideration for Go. One of the main reasons I don't want to tackle (1) right now if the possibility of benefiting from XRay even though it doesn't sort the case out for the vast majority: the gc users.
Two. The URL is a constant that is guaranteed not to return an error. It is not brevity.
Anyways, the point is I don't understand the point of err != nil bashing here, given there are two programs in the article that only contain one error check each.
I had a big group of coworkers from EPFL when I was working for Google Switzerland. At some point, I actually questioned whether we have a bias for these schools.
EPFL or ETH are definitely not something I'd consider as just "Swiss education system". These schools are what Stanford or Berkeley are in their region, and are highly international.
There is not a single mention of Java at the Brillo announcement.
Irrelevant but flush your biases and assumptions down to the toilet. Java can statically compile to microcontroller architectures with minimal runtime footprint. Stop blaming the languages, blame the runtime implementations.
Google is building their own hardware, an embedded Linux distro is primarily a need at Google to support our hardware projects for a long time. But, for the first time, the industry is capable of building hw projects at scale. It's not surprising we reinforce our interest to get involved by opening what we're already doing.
Code instrumented with OpenCensus can export to any backend by changing the registered backend.