2,179 karma · joined July 30, 2012
matt@matt-rickard.com
Think of the futility of ex-FAANG engineers who try to implement similar technology (e.g., reproducible and declarative build systems) at a 10-person startup.
I'm glad the author touched upon some of the outsized contributions Heroku made to DevOps and infra. I don't think many will argue with that. I was actually thinking of Vercel when I wrote the piece. What does a PaaS need to look like in 2022 to succeed? The author briefly mentions the current state of Heroku -- I think we all will also agree they deserved to capture more of the value that they created. The bigger question (in my mind) is how?
My personal blog with 327 posts. I write daily posts about engineering/startups/and other topics I find interesting (math, cryptography, behavioral psychology, etc.)
If you're looking for customizability (boot image, docker version, container runtime), minikube is probably your best bet. It even comes with some rudimentary file-sharing and port-forwarding primitives, but it isn't as batteries-included as Docker desktop. On the other hand, you have full ssh access to the VM to do whatever you want (+startup scripts, etc.)
Awhile back, I wrote up a comparison of all the Docker Desktop Alternatives. [1]
[1] https://matt-rickard.com/wordle-whats-the-best-starting-word...
diff3 is not
- idempotent
- semantic
- stable (formally, stability means that there exists a constant such that for small enough changes there is a guaranteed small merge)
[1] https://matt-rickard.com/diff3-shortcomings/ [2] https://matt-rickard.com/diff-the-magic-behind-version-contr...
Kata containers are essentially lightweight virtual machines. Obviously some differences but I'd bundle them in the category as Firecracker.
After minikube I wrote skaffold, which is a closer alternative to docker compose for Kubernetes with file watching and automated rebuilds and syncs.
All models are wrong, but some are useful.
Distribution is difficult. I think that's more of a marketing issue than a technical one (although just as difficult). Will put that on the list for a future post.
It's usually project dependent, but finding users on Twitter who are having difficult with your project, or even taking some of the advice from Part 2 and being a plugin to a bigger ecosystem can capture users.
(2) It's one of the main products of a venture-backed company. At Google, at the time, it was tough to get engineers on products like minikube.