![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
This sentence is the uncanny valley for structure.
This sentence is the uncanny valley for structure.
Your security people have not forgotten about appimages. It fills their nightmares.
I think no one said it needs to be ON a distro’s repos. That’s a straw man.
A package should be available in a native package format in a way that doesn’t cause conflict with what’s in the official repo. The reasons for a single source of truth on installed status should be obvious; but given the format of some packaging and the signed assurance of provenance, thr advantages to a native format can be leaves ahead of even that.
Wow, is this meme a really naive take that is contradicted by - oh god, everything. Can someone know about enterprise Linux and also be this naive?
Well we know where you stand on the Taiwan/China question.
Fucken is short for fuckeng, right?
Huawei paid good money to the people who stole that tech from Canada.
well-know
itself, that
close-source
to make […] works
Did you need to proof-read that again?
The uae is a huge concern. Their terms demand they get to see your code. When the vPBX company I worked for tried to get into the uae, it was a 10mil boondoggle that ended up ruining them.
The security software I maintained had one engineer.
Your move, sec nerds.
Back to webnames for you.
“unchanged” isn’t “unmaintained”. Wow, that’s a really short-sighted take.
You’re starting to understand the accidental wins in Enterprise software
Just pining for the microgravity.
I don’t prefer proxmox, but I will say that when you have even a machine with 8 or 16gb RAM, virtualizing a workload on it just makes sense. At that point the cost is 12% resources, and the benefits IMHO farrr outweight that.
expensive piece-of-shit (enterprise) systems, since they sometimes explode if your server changes interface names.
At no time in the past 25 years with Medium Iron have I seen something blow up on a reboot because an interface comes up late. We’d solved the issue of unreliable init order in 1998 - RH6? Zoot? Compaq, Supermicro, even embedded stuff on was-shit/still-shit gigabyte mobos. /etc/udev/rules.d handled this reliably, consistently and perfectly. Fight me.
so does RPM.
Careful. Jeff’s format gives us really great advantages from an atomic package that we don’t have elsewhere. THAT, at least, was a great thing.
Lennart’s Cancer, though, can die in a fire.
It’s amazing how many linux problems stem from ‘Redhat, however, found this solution too simple and instead devised their own scheme’. Just about every over complex, bloated bit of nonsense we have to fight with has the same genesis.
Ansible can be heard mumbling incoherently and so, so slowly, from the basement.
Remember who saw apt4rpm and said “too fast, too immune from python fuckage, so let’s do something slower and more frail”. twice.
Running
npm install
would give me a mini heart attack
It should; but more because it installs things right off the net with no validation. Consistency of code product is not the only thing you’re tossing.
It’s not the product, it’s the cavalier consumption of unsigned add-ons despite knowing better.
Typescript, VS Code, and DotNet Core
Aren’t these all just its own products?
And wow, do I hate VS Code. Just sayin.
Boeing: “how can we make the shittiest, most plasticky cramped hellhole ever imagined in the sky, even worse ?”