695 karma · joined September 1, 2009
brian.endofmyusername@pepsico.com (for work related stuff) or brian@endofmyusername.me for personal/hacker stuff.
Also, presumably you're talking about new laws in the US here? What stops businesses from just moving their HQ overseas to places with different laws they like better?
Julia talks about it in your quote above, but she says not to "act surprised", but she doesn't mean act as in fake, or feign, she means the action of expressing surprise. Another good reference is xkcd[0]. The point is not whether you're surprised, but the chilling effect that the judgment that someone should have already known this thing can have on their confidence, willingness to admit to not knowing things, and to the social dynamic of interacting with you.
[1] https://hueniverse.com/2012/07/26/oauth-2-0-and-the-road-to-...
ky is definitely still just in the "maybe useful/maybe practical" territory, but now that the basic concept of compiling from a Procfile seems to work, I suspect adding some configuration and more environment aware and extensible/overrideable templating could make it pretty practical, but I also had/have my eye on Helm. There may be some practical/logistical complications in using Helm, and I think if we went that way we'd probably go full hog and use Deis Workflow (https://deis.com/workflow/), which also deserved mention in this thread's discussion, but the k8s clients like the python one you point to or the ruby one (https://github.com/abonas/kubeclient) may be worth bringing into the mix depending on how this all works out... Thanks for the links and for having a look!
[1] https://github.com/awslabs/chalice [2] https://github.com/fabric8io/funktion [3] http://www.open-lambda.org/
For better or worse, we're going the full kubernetes route though, and still working out what deployment etc looks like. So far a lot of un-DRY looking YAML files have inspired a spike at a tool to help manage creating and maintaining kubernetes yaml[1], which others reading this are welcome to try and I'd love to hear better alternatives to or get feedback/pull requests/etc. I may push up a branch I'm working on later that partially automates creating deployments from a Procfile, but we discovered having seperate Procfiles may make applying env-variable only changes harder, curious to hear if others have any guidelines on that, it's so easy to edit an ENV var on Heroku we took it for granted.