I don't understand how podman can be used for serious development work. Sure, if you want to be bound to one single platform (linux), and create a bunch of individual files, you can sort of get something a little bit like compose.
But the beauty of compose is the same as the beauty of the Dockerfile. Portability, reproducibility (mostly), and a single readable file with all the relevant parts. It means a developer can use the same compose file locally that's used for deployment.
How do people actually work with podman? Do you work with a team? How do you setup a local development stack the way you would with compose?
The one big reason I dread giving up compose files is that they're a great way to have system agnostic documentation on how to setup a new stack. That means every developer can just start the thing locally, and it's pretty much the same as on the server (and everyone elses laptop).
Podman doesn't officially support any thing platform agnostic. How do you (or anyone) deal with this for a project in active development?
It's not just mildly annoying, it completely ruins a great thing.
Docker Compose is to stacks what Dockerfiles are to a single application. Podmans solution is to not commit to compose, but instead to create a bespoke mechanism involving a bunch of tiny files, all of which is insanely system (linux) specific, and therefore completely non-portable.
I genuinely don't understand how someone can see the value of Docker, but then do things so completely "not-docker" when it comes to deployment/stacks/orchestration.
What's the alternative? Everyones up in arms, but I see ZERO viable alternatives proposed.
If you have 1000 applications for every job, and you know that a bunch of these applications are "a bad fit", to put it mildly, you have to filter. And you cannot realistically give every resume a good, human look. By the time HR would be done, the market has already moved on five times.
So, what is the real difference between being overlooked because HR could only look at the first 100 resumes, or the AI filtered all 1000 resumes down to 100? In the end, a fuckton of potentially great people get their feelings hurt either way.
At least in the case of solar and EVs, it's a case of western countries preferring to protect their existing cashcow industries rather than invest to build the industries of the future.
For a brief second, Germany was in a position to become a solar power global player. But our conservative government was more interested in protecting their local, bad industry. Including destroying forests for coal all projections said we would never actually need.
I mean, can the market really handle any of these prices? If we're truly stuck with these increasing prices for another year or so, whole sectors might get "restructured", including gaming, simply because people cannot afford the devices they depend on.
So a tiny tiny tiny amount of games, with the added fun that older games might just not be available, OR cost a whole bunch because they're collector items.
People love talking about console exclusives, but every game from before 2013 is basically a PC exclusive.
Obviously I can't see the future, and I live in my own bubble....
Isn't self hosting, and small, private/semi-private communities the only way forwards for much of the internet? AI has made content extremely valuable, which in turn has started to destroy the openness of the web. Things are getting more and more siloed, with entry fees.
There's a world where self hosting comes back in a big way. AI ironically makes it much easier.
That's a foolish thing to say because building enough nuclear, even with the fairy tale prices and times people make up, would take soooo much longer and cost sooo much more than green energy.
Even more importantly, it's very hard to compromise and downscale a project when the inevitable fossil fuel lobbyists vote against you. It's a lot easier to half a solar park project than a nuclear project.
What choices make nuclear expensive that we could actually get rid of WITHOUT IMMEDIATELY increasing risk (which is low because of regulation)?
Moreover, it's crazy that so much regulation was provably written in blood paid by workers and public after a company got greedy. Sure, let's build 50 AND reduce regulations.
Finally, the biggest fucking thing: It is MORE expensive NOW than the green alternatives, AND green energy has proven over the years to actually keep it's promises of improvements, compared to fission and SMRs, which are always just 5 years away.
So its really safe, but also the evil regulations make it expensive. I'm certain there's ZERO correlation between regulations that make it expensive and regulations making it safe....................
So, where is the free market shitting out nuclear power? Anywhere?
Well, business english IS annoyingly verbose and full of empty phrases. It would be cool if we could dispense with vapid pleasantries.
I'm certainly not going to be the first to stake my job or my promotion on that particular hill. So I can fully understand why people will still turn "We need the database changes ASAP, you promised they'd be done. Get it done!" into half a page of drivel.
They don't have the same quality and kind of data. For example, Claude Code might have general conversation flow data for implementing feature X, but Cursor has users individual editing actions AND the chat flow. Which line did the user manually edit after the agent did it's thing? What's the commit message (if done manually)? Stuff like that is worth it's weight in gold.
It's really important to note that the programmatic vs. interactive framing is a little misleading. For example, if you're using some IDE integrations, that is still interactive, that is still the same usage pattern as using it in the Claude Code CLI. BUT with these new rules, it'll count against this special "programmatic" usage.
Considering what kind of fuckups happened up until now everytime Anthropic vibe codes a horrible anti-automation "fix" (like billing extra usage just because the string "hermes" exists somewhere in the prompt), this will get funny/horrible really fast. After all, you can very easily script tmux to use Claude Code "interactively".
What crazy shenanigans are gonna happen? Are people that type too fast, or people that copy paste too much, or people that output to markdown/json too often going to wake up to a 800$ extra usage bill or a banned account?
People do want the advantages of decentralization, but they don't want to pay the price for it. Even worse, centralized systems are great for most of the time, the pain generally happens only in a short span, but then very intensely (imagine a merger and a sudden price spike). Decentralization is a little bit of pain all the time, for a lot of happiness only in the rare case where the centralized alternative collapses.
Obviously, there's different options and variables and bla bla bla, but considering how consolidated and highly industrialized and standardized meat production is, this data is very likely close enough to true for the wast majority of beef burgers eaten by the people complaining about AI resource consumption: https://ourworldindata.org/environmental-impacts-of-food
Well, I've got a small server rack and roof top solar, therefore data centers don't actually use water.
In other words, bringing up some anecdotal, hyper specific (how many meat eaters just "have a few cows"?) information says absolutely nothing about the truth of the matter, but a lot about what you believe constitutes an argument.
But the beauty of compose is the same as the beauty of the Dockerfile. Portability, reproducibility (mostly), and a single readable file with all the relevant parts. It means a developer can use the same compose file locally that's used for deployment.
How do people actually work with podman? Do you work with a team? How do you setup a local development stack the way you would with compose?