That’s neat how that’s been a standard feature of enterprise Linux for 20 years. They call them alt-packages and, even before a succession of environment juggling and subversion swapping, they worked really well.
(Still do, except all the people who knew how to figure dependencies have left RH. I’m looking at you, Ansible who will soon need containers for even client install)
I presumed the draw of us-east-1 was its lower cost
At no time is pub-cloud cheaper than priv-cloud.
The draw is versatility, as change didn’t require spinning up hardware. No one knew how much the data costs would kill the budget, but now they do.
universal single point of failure.
If it’s not a region failure, it’s someone pushing untested slop into the devops pipeline and vaping a network config. So very fired.
I love the “git gud” response. Sacred cashcows?
No jack? I’m out. This is partially a preference but more I don’t want to be forced into the bt earpod purchase loop.
it feels like the setup menus are just a game of minesweeper
…and that turns it into a skills game vs a bad gamble.
And people who don’t wanna hire pros to manage their on-prem think they can maybe, just maybe, win that skill game.
And that’s how casinos that don’t launder their games of chance through clowd sign-ups also leverage dunning-kruger for profit.
This looks very nice.
Um, you know you’re supposed to keep dev tools in dev, right? Npm->commit->release payload without npm. Far fewer supply-chain exploits.
Still crutching on containers?
minimum spends
When you’re not on the car lot, the word is “budgets”.
… Carefully and with caution.
Choosing packages by popularity? Is that like choosing physiotherapy clinics by the font on the sign?
Systemd detects problematic software? Bit of pot-calling-the-kettle, there.
Comma splice akimbo.
This isn’t about people choosing one bad voice chatter over another. This is people who can’t bother to use the best tool for the job.
(And web fora aren’t it)
There was 25 years between c;m;mi and lennart’s cancer, filled with excellent choices better than either.
From a security and os build perspective, they’re all absolutely horrific.
please see the changelog inside the app
Is the hope that, after updating and checking the changelog and deciding that updating is NOT for you because of some idiotic breaking-change, you just hop in the time machine and prevent yourself from updating ?
No need to look up how to do a clean install.
The suggestion you don’t know that enterprise OSes have been doing clean installs and removals of a product and all its dependencies for 25 years as a critical test before issuing said packages suggests you’re working around too many problems without solving them.
We did devops by pxe-based kickstart and then simple package updates before devops was even a word. It still does better than Ansible does now.
I maintained a VPN tool for years.
I also worked as OS Security for a company that was paying MANY people to maintain an enterprise Linux distro and all the parts in it, based on their ridiculously deep knowledge of the Unix kernel and Unix apps. I will never have a job or a mission half as awesome as that was. And for the linux dev labour the company helped finance, it shouldn’t be so hated; but it is.
Not being paid for the time? Not using company gear? No problem.