tool

Aside from the callback chains and API shit, my issues with Node rest almost entirely on the lack of a standard library, because that led to the state of NPM today, which is just an absolute garbage-fire shitshow as far as I'm concerned.

I have my own separate issues with NPM, namely its dependency resolution (my God, just take dnf's dependency resolution algorithm and use it), trivial packages that other packages list as a dependency (is this an int? Is this running on Windows? Better take this one line and make it a package!), and the relative inability to remove a package from a registry (did a secret slip in there while testing? Tough shit!). The worst of that being the trivial packages, I think, because then you can end up with projects that can have a dependency tree 10s of thousands packages long.

And all that bullshit wouldn't be even 1/16th of the problem it is today if there were a standard library.

You should take what I'm saying with a grain of salt, though, I'm just a DevOps Sysadmin, and aside from running some software that uses Node, most of my experience with it is unfucking it when our devs come to me to fix the tangled monster they've created.

It only costs $6 a month plus the $35/yr for the domain name

My man, you are getting absolutely bent over a barrel by your registrar. You could get that domain significantly cheaper at a place like Porkbun or Namecheap.

just raise awareness about tools like this one https://lemmyverse.net/

I also think that something like LCS or Lemmony should be recommended and/or included in the default Lemmy docker compose file.

That way, when new Lemmy servers get spun up, they will automatically get seeded with content and communities from other existing Lemmy servers.

I've had something similar happen, except the post that I found which fixed the problem was made by... me. Apparently I'd had the problem before, figured it out, and then posted an update about why it was happening and how to fix it.

That was some Twilight Zone shit.

At that point you may as well go full Vagrant or start using Docker images.

And no matter how quirky or obtuse venv/conda/pip can be, they will never be as bad as Node. Ever. Node will hold that King Shit crown forever, or at least to God I hope it does.

Something worse than Node coming around and getting popular might just make me quit IT altogether.

At work/for business, you can't beat Veeam. It's the gold standard and there is literally nothing better.

At home, Duplicity. Set it up once and then just let it go, and it supports a million different backup targets you can ship your backups off to, including the local filesystem. Has auto-aging/removal rules, easy restores, incrementals, etc. Encrypts by default too.

Github Copilot is worth the money. I've had it finish out functions for me after just a few lines. There's usually an error or two, but the consistency with which it can predict what I'm doing or trying to do is pretty impressive.

I pay for it just because it's cheap and to support them

I did this too when it first came out, and then the product became robust enough that I recommended we implement it at work because secrets management was non-existent. We have a bunch of licenses on the Enterprise plan now and it just keeps getting better each update.

My only complaint is that migrating the data to a new server is a pain in the ass and never works correctly, even when following the migration instructions to the letter. Always have to open a ticket with them for that. Not enough of a pain to move to another product, though.

I also still pay for my personal plan. It really is a fantastic product.

That's exactly why we need to give them the boot.

Hard disagree. If you're running something business-critical, the support that you get with a RHEL license {or any other vendor, for that matter) is worth its weight in gold.

If you can't fix something, you don't want to be looking for solutions by sifting through forum posts directed at home users when the business is losing thousands of dollars per hour. That's what the license is for, and that's what you pay for.

We've known about the principle since 1856, and have known about its possible impact since 1896.

The worst part of ML is Python package management

Do you have some time to talk about our Lord and Savior, venv?

A few jobs ago, we had a fleet (2K+) of mobile inkjet and Zebra printers that we were responsible for for some ungodly reason.

The Big Blue Sledgehammer from Lowe's was the official method of decommissioning them per the IT disposal policy. That I wrote.

That's the only thing I miss about that job.