holoway

9 ms·

61.
by holoway 6y ago
It’s working pretty well for everyone. OpsWorks revenue was smaller than Chef. It grew our pie. Elastic, Redis, Mongo - all far bigger businesses with AWS competitions with them, seeing big growth in their cloud businesses. Having AWS, Azur
62.
by holoway 6y ago
I’m Adam Jacob (the quoted person in Matt’s article). Happy to answer questions :)
63.
by holoway 7y ago
Every thread here about how it’s vanity is bananas. They’re going to build computers! With software to go with them! So that you can have the same experience that the hyperscale companies do. It’s a great bet. This isn’t a blitz to help wit
64.
by holoway 8y ago
Every person can decide for themselves what story they want to tell. Chef has been declared dead/dumb/irrelevant from the beginning. It’s doing great as a business, and as software. You play your game - y’all can think it’s irrele
65.
by holoway 8y ago
They aren't claiming to make it open source - they are making it open source. I explain my perspective on the motivation here: https://medium.com/@adamhjk/goodbye-open-core-good-riddance-...
66.
by holoway 8y ago
Historically the answer is nothing, or very little. The commercial products have a licensing mechanism that nags you, or at least it did. I don't know what their plan is on that - but I know they'll do it in public now. :) Since e
67.
by holoway 8y ago
I'm not involved in the day to day of the business anymore, so I don't know. I suspect now is a good time to talk to a sales rep and see what they can do.
68.
by holoway 8y ago
Happy to answer questions about it, if anyone has any. :)
69.
by holoway 8y ago
Original author of Chef here (although no longer with the company day-to-day). I would not assume that - 100% of the software Chef produces is open source, so no reason to ever differentiate on features in licensing. So I doubt they would r
70.
Free Software Is the Only Winner in Elastic NV vs. AWS(medium.com)
5 points by holoway 8y ago|0 comments
71.
by holoway 8y ago
I think we agree (and it's probably self evident) that it's hard but necessary work to try and get the boundaries right, and it requires a lot of refactoring before things stabilize. In the early stages of work, that refactoring i
72.
by holoway 8y ago
Disclaimer: it depends. :) Since that's not a good answer at all, I'm going to write the rest of this as if I have the answer, even though I know I do not, because it's deeply situational. Equal care does need to come from th
73.
by holoway 8y ago
Author here. The Right Way :tm: is situational - there isn't one right answer to things like when and how to make contracts, or how to break them. When I used the term "force", you'll see that I'm usually talking ab
74.
by holoway 9y ago
Habitat uses some simple data structures that are basically CRDTs. We used them because they made the user experience better (not needing infrastructure other than the gossip itself). One thing I learned early on that journey was that the m
75.
by holoway 10y ago
Sure. Habitat's supervisor is a very low-level thing - it manages the lifecycle of your service, participates in the gossip ring, etc. That means a failure at runtime of the supervisor is pretty unacceptable, and similarly, you don&#x2
76.
by holoway 10y ago
We're totally going to do it.
77.
by holoway 10y ago
We struggled with this! I think we found the right balance, but time will tell.
78.
by holoway 10y ago
Nope! You can use it with docker, and we think it makes the experience better. We love docker.
79.
by holoway 10y ago
This is Adam - Rust has been amazing to work with, and was the prefect choice for this platform. It's great.
80.
by holoway 12y ago
Ezra was so good to me. He helped write Chef, tool our idea and ran with it as a critical part of Engine Yard cloud. We wrote chef solo together . He and his wife made my wife and I feel warm and welcomed in San Francisco. Rest well, big gu
81.
by holoway 12y ago
From my (admittedly super ignorant position) it felt very similar - message passing, spawn, etc. The primitives felt very similar. I'm sure they differ hugely in details ;)
82.
by holoway 12y ago
Yeah, I was doing this for fun. I'm pretty secure in my day job. :)
83.
by holoway 12y ago
It's absolutely lightweight. First impressions for sure, writing what were very small programs. I tried to be clear about that. :)
84.
by holoway 12y ago
I am absolutely quite (completely) new to both languages.
85.
by holoway 15y ago
Also, Pallet is sweet - I (Adam Jacob, one of the authors of Chef) have talked with Hugo, looked at the code, and played with Pallet. It's good sauce, and it's not quite the same kind of beast as Chef/Puppet. It's much more like what the lo
86.
by holoway 17y ago
As one of the founders of Opscode, and of Chef, it's crazy to say that the reason we started Chef was because we didn't want to buy a support contract. We have no beef with Puppet - from our experience building fully automated infrastructur