The question was why Podman doesn’t have the adoption levels that Docker does, and my supposition was that (for those that don’t have much Linux administration experience) added steps like systems configs, or quadlets etc are just another barrier to entry that you don’t have with Docker.
I’m not arguing that Docker is better (I think Podman wins in a lot of ways actually) just that Podman requires a bit of extra work to implement well and that is just enough of an annoyance to tip the scales towards Docker.
> Doesn't quadlet fix some or all of those problems?
It definitely can solve some of those problems, and that’s the approach I’d generally recommend.
But to answer OP’s question - my supposition was that the mere fact that such a device is even necessary (when compared to docker) is an added work that isn’t obviously easy to implement for someone who is just trying to learn how to containerize their app (and might be a developer but not that experienced with Linux administration) and this one of the main reasons Podman isn’t as popular as Docker.
I think Podman is better in a number of ways, but it isn’t the most intuitive to implement compared to Docker.
Linux. It’s not the installation of podman that can be fiddly. It’s the setting up systemd unit files and local user accounts for rootless / daemonless deployment of containerized apps that can be a headache.
I’d wager it’s mainly just that deployment is mildly more annoying and requires more disparate steps.
Especially if you want to go rootless (and you should).
For someone that isn’t “Linux first” (like a baby developer learning to containerize their apps), the idea of dealing with systemd unit files or kublet configs, and having to created dedicated local service accounts (and remembering to enable linger) is somewhat intimidating when compared to just installing docker, whipping up a docker compose file and pressing “start”.
I understand why they’ve taken this approach but it’s pretty clunky and a bit unfriendly.
Yeah - answered below. As I mentioned, a lot of the tweets and Reddit posts have been deleted so it’s hard to track down now. It was a bit of a shitstorm on Mastodon some months ago though.
Yeah. It’s trace now because many of the tweets and Reddit posts have since been (unsurprisingly) purged but it looks basically the same as what we’re discussing regarding Mullvad right now.
There’s obviously no single solution, it won’t make sense for all use cases, but NATS is far more lightweight, very simple to configure and deploy, has very few dependencies and offers incredibly low latency. NATS with Jetstream also closes the gap even further.
Kafka still wins for very large data pipelines (hundreds of terabytes or petabytes), complex stream processing, or very long retention requirements for messaging.
If you’re mostly streaming messaging between micro-services though (or if you’re currently doing a lot with MQTT) NATS is very likely the better move.
That said, anyone trying to build something new where Kafka might make sense should probably be considering NATS as an alternative - particularly with micro services in mind.
Strong agree that Flickr went downhill rapidly when acquired by Yahoo - but also happy to report that it has since bounced back.
The community isn’t the same of course, but the platform itself is a joy to use again - especially as someone who got tired of Instagram when it stopped being about photography.
No. It’s a component of Davinci Resolve, not an isolated binary. It’s not likely ever to be offered as a standalone app. That’s just not how Resolve is designed.
Yes. The free version is very generous. Most non-professionals won’t ever need a license for Resolve Studio.
BMD’s entire game here is that they are a hardware company first.
They hook you in with some really good software - and when you start getting in to professional workflows that requires specialized hardware (I.e. capture cards, I/O devices etc) you’re locked in to needing to use BMD hardware.
So it doesn’t cost them a great deal to offer the free version to most people because they have to have the software anyway to support the hardware.
Also, while they certainly make a profit on the studio licenses, it seems to be largely because offering those advanced features have costs they can’t eat. For example, the official (and expensive) Apple ProRes encoder SDKs, and advanced tech behind their noise reduction plugins among others.
The FAA very clearly has jurisdiction to “all navigable airspace” which is broadly defined as “all airspace immediately above ground level”.
Which is to say, there’s no minimum height threshold under which you could fly a drone (outdoors) where the FAA doesn’t have full legal jurisdiction.
You can say you feel it’s overreach, but it’s well established that the courts do not agree.
Having said all of that, I definitely agree that the states have been doing a pretty shit job of asserting their rights across the board.
Of course it isn’t just individual states. Congress as a whole has been happily ceding power to the executive branch for a few decades now - which is largely how we’ve gotten to this point.
My approach might be an outlier, but I’ll share since it’s a bit more platform agnostic.
I do almost all of it work in the terminal, so I had already been using chezmoi to manage my dotfiles for a few years. Eventually I added an Ansible bootstrapping playbook that runs whenever I setup a new environment to install and configure whatever I like.
I’m already living & breathing Ansible most days so it wasn’t a heavy lift, but it’s a pretty flexible approach that doesn’t bind me to any specific type of package manager or distro.
They’re also developers and probably do care. I’d wager, as always, someone in management with bonus targets to hit probably told them to do it anyway. :/
I WANT to love it - and if I was only ever working on one, or a small number of systems that I was the only one working on I’d probably do it. I’m ALL about customizing my environment.
However ssh into various servers through the day (some of which are totally ephemeral), and having to code switch my brain back and forth between vim mode and emacs mode in the shell would just slow me down and be infuriating each time I connect to a new box.
The question was why Podman doesn’t have the adoption levels that Docker does, and my supposition was that (for those that don’t have much Linux administration experience) added steps like systems configs, or quadlets etc are just another barrier to entry that you don’t have with Docker.
I’m not arguing that Docker is better (I think Podman wins in a lot of ways actually) just that Podman requires a bit of extra work to implement well and that is just enough of an annoyance to tip the scales towards Docker.