rpercy

My 2 cents is that Kubernetes introduced a very powerful lifecycle for operating workloads that has enabled the automation of a wide variety of tasks.

But the abstractions are still relatively low level. The Ingress API in particular is a known issue and currently being simplified.

Oh, very cool. Will definitely check out guru. Thanks for the tip.

Not really. In a language like Java, some of the questions I'd have to ask myself are:

  - Should I try to catch the exception, or just let it 
    bubble up and edit my interface to include it?
  - Should I create a new exception type or reuse an existing one?
  - Should I throw a checked or unchecked exception?
  - Am I exposing implementation details via my interface? 
    (eg I don't want to throw an SQLException from GenericDataSourceWidget.connect())

I've been using the Gogland beta for the last few weeks and it's been quite stable. For large codebases, it's hard to beat a good IDE's ability to quickly jump between symbols (go to definition, find usages, etc).

100% agree re: readability (as I've mentioned elsewhere).

I've actually been very surprised at the near-ubiquity of Go in the modern infrastructure/tools space though. Seems like each new OSS product I evaluate is written in Go. See companies like Cloudflare, Hashicorp, InfluxData, CoreOS, and, obviously, big projects like Kubernetes.

I'm with you. IMHO, Go's simplicity is its biggest virtue. It has fostered a community that values consistency and clarity over syntactic sugar. And, as a result, I find each new codebase extremely accessible.

Heh, it does feel repetitive. But after ~10 years with Java, I'm happy to avoid the cognitive load from deciding how to most politely generate/propagate an exception. Obviously, there's no perfect solution, and preference is subjective.

To each their own. I enjoy writing Go almost as much as writing Python. But more importantly I find reading Go easier than any other language - mostly due to its explicitness and consistency between authors. That has made it much easier to dig into code bases that solve some very complex and interesting (to me, anyway) problems.

Also, I assume the 'no type safety' statement is just hyperbole?

Do you have an example of the community celebrating mediocrity?

My impression is of a community willing to go without some features, in order to preserve those it values. Namely simplicity, explicitness, terseness, and consistency.

FWIW, I'd be quite interested in paying, but I'm hesitant to provide my credit card to a website with no track-record just to evaluate their product. I'd happily provide my paypal info though.

"if you want to be popular you just need to put out more content instead of trying to improve the quality."

Not quite. What he said was: to be popular, improve quality until it stops making a difference (flatten the slope). Then make sure you put out enough content.

Agreed. Another possibility would be a hybrid approach with delivery trucks acting as mobile distribution centers. Trucks could be loaded with drones and packages, park in rural areas and let the drones take care of the last mile.

What do you think of a service like http://keycafe.com/? Rather than picking up your package from a lockbox, the delivery person would grab your keys from what's essentially a lockbox.

something = Django. http://www.djangoproject.com/

I've been running Ubuntu on a Dell Inspiron for over a year with no trouble. Given recent events, I would say Dell is a pretty safe choice for Linux users. Definitely go for the nVidia graphics though.