nyangosling

>It made sense that, if we were going to stay on Python for the next ten years, we should invest in the latest version of the language.

I don't know this stands out to me in particular, but the 10-year commitment is definitely a big decision. I suppose I've never had to make a similar decision so perhaps this is more common than I think.

Are there not aspects of industry regulation at the legislative level that don't really have to do with what the public wants already?

This is a very serious moment for Docker the technology vs Docker the company. It's important that this discussion is happening, and I don't necessarily think that the only result is a hostile fork--a cooperative fork here is possible. Docker has done a lot and they should continue making great services around the core technology, but that needs to be balanced by the ecosystem it's part of.

Good, that's the way I like it.

I think this story is actually a pretty incredible one. Just logistically it's a very interesting story that they were able to keep their collective corporate mouth shut--and even though it seems they're gearing up to milk the marketing effort now, that they did this without immediate payout in terms of brand marketing is surprising. And it's not like we're talking about a processed food brand with a million variants on the shelf either--we're talking an iconic, one-note Kraft dinner.

I'd inquire about the taste, if it's any different, etc, but I haven't had Kraft in, uh, a long ass time.

From Pivotal/Cloud Foundry, this was just announced at Sam Ramji's "The Makings of a Modern Application Architecture" keynote at the O'Reilly Software Architecture Conference.

Oh sweet baby Jesus it's back.

My whole office is in RTP and we're all down. Our website is stuck on loading "googletagservices" so... walp.