I can confidently say that the Jellyfin team intend to raise the price 10x the previous price.

The recent attacks have been against the AUR.
Which pacman doesn’t reference.

In terms of sneaking in malicious code, that’s possible in the official repos of all operating systems, including the windows store.

The actual meme speaks more to the fact that windows update is enforced unless you jump through enormous flaming hoops, and it will measurably make your already running system worse as it forces the installation of things the user wouldn’t want (ie copilot) or removes functionality they do (classic control panel).

But you know… I use Arch btw.

This is pretty much what an American Staffordshire Terrier looks like, they are famous for that smile.

They are also famous for destroying things as puppies.
Mine tore apart the old couch we had on the back porch for him to sit on.
So we threw it away and sourced another free one from the side of the road.
Which he then tore to shreds.

Incredible animals; love humans, hate other dogs, need training.

These are pretty calm messages to an Australian and Garry is British, so culture checks out.

// What the fuck
// Fuck dynamic compiling.
// what the fuck is this shit
// What the fuck, why isnt this a method

Should this by the by commentary be there?
Not really.
But as a programmer, I understand each and every time I see something like:

// Urgh this is so dirty, Invalidate() and Refresh() do nothing.
tButt.AutoSize = false;
tButt.Width = maxWidth;
tButt.Height = maxHeight;
tButt.AutoSize = true;

If you can log into the site, it’s done.
If you try to access the site and you get a “startup log” page, it’s still ongoing (and it will show you there what it’s doing).
https://jellyfin.org/posts/jellyfin-release-10.11.0/#startup-ui-and-log-viewer

I think the feel from the Devs is that there isn’t enough new functionality to justify the major version bump, this primarily being a reimplementation of existing features.

BUT, I agree with you, it should definitely be V11 under the semantic versioning scheme.
Whilst there is a migration path here, the database changes under the hood alone are likely to break backwards compatibility with all plugins (with in-house plugins being upgraded in sync).
Such breakage is kind of the defining characteristic of a MAJOR version.

If you “vibe code” your way through trial and error to an app, it may work.
But if you don’t understand what it’s doing, why it’s doing it and how it’s doing it?
Then you can’t (easily) maintain it.
If you can’t fix bugs or add features, you don’t have a saleable product - you have a proof of concept.

AI tools are useful, but letting the tool do all the driving is asking for the metaphorical car to crash.

This is fantastic.
Tradie doesn’t want to be watched while they work.
I want to learn by watching, so I’ll hire someone else.
We both get what we want.

Sounds like you’re stuck in a worst practices mindset.

Worst/Pragmatic.
If I get a timeline for a feature request, then everything can be scheduled, tested, whitelisted, delivered at a reasonable time.
That’s the rarer event - normally it’s more like “the scale head has died and a technician is on the way to replace it” and whilst I modify the program in question to handle this new input, hundreds of staff are standing around and delivery quotas won’t be met.
Is my position arrogant? This is the job.

Sign your damn releases and have the whitelisting done by cert.

I’ll see if this is possible at the site in question, thank you.

It IS bespoke internal development, not for deployment outside of the facility.
The computers running the software exist only to run this software and have no business talking to the internet at all.
IT is provided by an external third party vendor who operate on an inflexible “best practices dogma”.

In a rapidly churning startup phase, where new releases can and do come out constantly to meet production requirements, this one size fits all mentality is impractical.

If you refuse to whitelist the deployment directory, you will be taking 2am calls to whitelist the emergency releases.

No it can’t wait until Monday at 9am, no there will not be a staged roll out and multiple rounds of testing.

I am more than willing to have a chat; you, me and the CEO.

This requirement is designed to be hard, and as such is a major red flag to me.
What else is this company going to be difficult with?
Can i only get customer support or cancel my account in person, between 9-4 on the 2nd Friday of the month?
I would consider alternatives, if possible.