atzanteol @ atzanteol @sh.itjust.works

Posts

6

Comments

4,028

Joined

2 yr. ago

That was the part I found surprising. That somebody died from it. Maybe it wasn't diagnosed soon enough or they had comorbidities or something.

What if they start it?

This was the first recorded death from the disease in the county since 2007

... What?

I read a lot of advice online for distros, but my main needs are not really discussed.

You're not special and Linux distros aren't that specialized. They differ in packaging, upgrade philosophy, etc. There is no Linux distro that can't do the things others do.

You dabbled with Ubuntu. Stick with it, you'll be fine. Unless you really want mint, then go for it you'll be fine.

This needs to be pinned to every single "looking for a distro" post.

It's hard being a brownshirt.

The official declined to comment further “out of respect for the privacy of the family and loved ones” of the reported victim.

The Trump administration doing something out of respect? 🤣

That's awesome.

Nobody understands JavaScript. It's the quantum mechanics of the software world.

As a proper "gray beard" myself the utility of systemd vs. sys-v init scripts has always been blindingly obvious. 🤷

Dude - you gotta get off the snap hate train for a bit.

Do you not understand the difference between "hey, run this rando shell script on the internet" and "hey, use this standardized installer which may run some shell scripts"?

I don't give a shit about all the canonical hate. For me snap does what I want:

1. Installs things in a standardized way using a standard interface i can easily script with ansible
2. Provides a similarly standardized way of upgrading and uninstalling that can also be automated easily with ansible
3. Works "just fine".
4. Edit - I'll add in a fourth - creates a fucking binary I can run (no flatpak run something.something.something BS)

It's not bash I'm criticizing. Do you understand that? Because stop reading if you don't and go back through my list. I'll wait.

So good - you get that bash isn't the problem. It's the bespoke unstructured installer/upgrader/unisntaller part that is bad. You could write your installer in C, Python, etc. and I'll levy the same complaints. You want me to install your python app? It should be available through pypi and pip. Not some rando bespoke installer.

Ah - you have discovered my complaint.

That is precisely why I went with microk8s instead. I don't install software from people who can't be bothered to package their software using standard deployment tools which has been the correct way to distribute Linux software for decades.

They try this every 5 years or so. Microsoft gives them some short term discounts and they come running back back.

You've made this about snap. Flatpak, rpm, deb, etc. all work too.

You're welcome to make whatever bad decisions you like. I can manage snaps with standard tooling. I can install, update, remove them with simple ansible scripts in a standard way.

Bash installers are bad. End of.

They did their best, it's not their fault the guy was a bad shot.

Microk8s manages to install with a snap. I know that snap is "of the devil" around these parts but it's still better than a custom bash script.

Custom bash scripts will always be worse than any alternative.

I really want to push back on the entire idea that it's okay to distribute software via a curl | sh command. It's a bad practice. I shouldn't be reading 100's of lines of shell script to see what sort of malarkey your installer is going to do to my system. This application creates an uninstall script. Neat. Many don't.

Of the myriad ways to distribute Linux software (deb, rpm, snap, flatpak, AppImage) an unstructured shell script is by far the worst.

curl -sfL https://get.k3s.io/ | sh -

Never, ever install anything this way. The trend of "just run this shell script off the internet" is a menace. You don't know what that script does, what repositories it may add, what it may install, whether somebody is typo-squatting the URL and you're running something else, etc.

It's just a bad idea. If you disagree then I have one question - how would you uninstall k3s after you ran that blackbox?

Yeah - I did come down a bit harder on helm charts than perhaps I intended - but starting out with them was a confusing mess for me. Especially since they all create a new 'custom-to-this-thing' config file for you to work with rather than 'standard yml you can google'. The layer of indirection was very confusing when I was learning. Once I abandoned them and realized how simple a basic deployment in k8s really is then I was able to actually make progress.

I've deployed half a dozen or so services now and I still don't think I'd bother with helm for any of it.