@jmoiron@bryanl If anything was going to get named after me I'm glad it's a complaint.
@jmoiron@dgryski @PreetamJinka "I think I have that item on one of my previous todo list schemes somewhere, let me go through the history."
@jmoirongodoc w/ "godoc -http=:6060" is a great sanity check. If documentation is missing, doesn't read well, or the package exports too much, it's pretty clear. If the godoc looks similar to what you're used to in the stdlib, it's a good sign. #golang
@jmoiron@francesc That was just the earth rejecting your SF >> NYC tweet no need to be alarmed :)
@jmoiron@tmichelberger thanks! there are rel links for https://t.co/ED3T9MF6aS or https://t.co/PTBGWtL5bl but I guess modern browsers do not put any emphasis on this anymore :(
@jmoiron@cemerick I suppose the other way to look at it is that programming models were way out in front of hardware & concrete reality for a long time; eg. Simula was designed in 1965, Lamport clocks were designed _before_ DNS.
@jmoiron@dweomer @concourseci It's everywhere. It's not like these metaphors increase specificity, their context just has less overlap. We use "precision" to mean something specific in mathematics and it works out. I've long wondered if it was a marketing thing; if you own language g...
@jmoiron@PreetamJinka @pauldix you just gonna let this happen? :D
@jmoiron@clofresh That's definitely the sweet spot. Docker images also have a better toolchain, more vibrant community, and are more portable. 100% agree with needing more time to settle. I think eg. scheduling >1 process for the same running environment is ultimately solvable.
@jmoironA great reply to my post. I really admire a lot of people involved in the k8s ecosystem (many from interactions in the Go community) and that remains my biggest source of optimism for it. https://t.co/hLTHTgnBIm
@jmoironIs k8s too complicated? I wrote this and I still don't even know. https://t.co/gZxg9lF2Hv
@jmoironThis is a great quote. The irony is that, in context, it applies to k8s itself. https://t.co/xSSYyR4Gmd
@jmoiron@clofresh :(
@jmoironLets use YAML because it is simple like JSON so tooling is easy, and it also has comments! Oh, but we ever want to actually add tools to our process then they either will not preserve comments or will not be simple. Hmm.
@jmoironIt was the deployment for me. I can get used to living in hell, but I don't want to deploy there. https://t.co/s5yit57MBO