At Basecamp, we treat our company as a product. It's not a rigid thing that exists, it's a flexible, malleable idea that evolves. We aren't stuck with what we have, we can create what we want. Just as we improve products through iteration, we iterate on our company too.
This is a bit of a weird article to write. After all, there are a million projects that Linkerd doesn’t use, and none of those decisions deserve a blog post. But the fact that Linkerd doesn’t use Envoy specifically has become a common enough topic of discussion that it probably deserves a good explanation.
I’m a big proponent of GitOps— it is an approach that sidesteps complex tooling in favour of building CI/CD using a combination of Git and declarative configurations. I recently wrote an article about ‘11 Reasons for Adopting GitOps,’ but I also experienced the approach’s limitations on different client projects. Talking to the Humanitec folks prompted me to write about my negative experiences to help paint a more objective picture of GitOps and highlight another possible approach.
You can either rail against things you can’t change, or you can expand your skill set into new and bold directions that embrace the winds of change and position yourself to take advantage of them, whatever those might be.
They also clearly have a better integration story than AWS does since Google teams are apparently allowed to speak to one another in the company cafeteria. But that story remains weak at the introductory level—and that’s what matters.
So, what was tech’s big song and dance? Let’s remove offensive terminology from our collective lexicon. There were several casualties, white/blacklist are examples of words deemed to be too offensive to use. The change that caused by far and away the most discussion however, was GitHub’s announcement that they were changing the *master branch to main. This change was (is) to happen at some undisclosed time in the future.
Shall I migrate to Signal, Threema or Telegram? No, because they all have — WhatsApp included — the same problem: They are walled gardens. Imagine a world where for each mail recipient using a separate domain, I would need separate mail client? Or in other words: Gmail users can only communicate with Gmail users.
I maintain many open source projects on GitHub and elsewhere (over 160 as of this writing). I have merged and/or closed thousands of Pull Requests (PRs) and patches in the past few years, and would like to summarize here many of the reasons I don't merge many PRs.
I have never used WhatsApp, and never will. Despite this, I still feel the need to write an article about WhatsApp since it’s the perfect case study to help understand a class of businesses models I call “user domestication”. The domestication of users is high on my list of problems plaguing the human race, and is worth a detailed explanation.
In the old days, when Google (or any poorly tuned AI that Google unleashed) decided it wanted to kill your business, it would usually resort to denying access to one of its multiple walled gardens, and that was that.
Perhaps not quite forever, but the history with Docker feels really long in good and bad ways. I had joined Red Hat in the summer of 2015, the same summer that OpenShift 3.0 went GA. This was a remarkable event because it marked a redesign of the platform onto Kubernetes which itself had just gone to v1.0 (this is the same timeframe that GKE went GA, if you can believe it’s that old).
Über die Meldung, dass CentOS 8 zugunsten von CentOS Stream einstellt, habe ich mich sehr geärgert. Ich war sogar richtig gehend angepisst. CentOS war immer die Möglichkeit, eigene Dinge auf Red Hat Kompatibilität zu testen, ohne Subskriptionskosten (für das Patching) bezahlen zu müssen.
CentOS ist/war ein freier Klon von Red Hat Enterprise Linux (RHEL). Die vorige Version CentOS 7 läuft auf unzähligen Servern und Cloud-Instanzen. CentOS 7 war nie perfekt (bei Versionswechseln gab es Lücken in der Update-Versorgung, typischerweise im Bereich weniger Wochen), aber für viele war es gut genug — für den Produktivbetrieb kleiner Server, für den Unterricht, oder einfach, um ein RHEL-kompatibles Betriebssystem kennenzulernen.
Here’s the thing: I write open source software to solve my problem. I let you use my solutions because that comes at zero cost for me (well, almost, I still have to pay for the website, you are downloading from. You are welcome, by the way).
FoldFold allExpandExpand allAre you sure you want to delete this link?Are you sure you want to delete this tag?
The personal, minimalist, super-fast, database free, bookmarking service by the Shaarli community