What specifically do you mean when you say “Open MacOS”? Open to what? You can already install anything you want on it. It’s unix based, so your terminal works mostly the same as in Linux. You’ve even got a package manager (homebrew), so you won’t miss apt or whatever else you use. iOS is another discussion, but imho, OSX is “open” enough.

Superb write-up, well done! Echoes my experience completely.

Off the seven seas? Try Britbox. Relatively affordable, no ads whatsoever. They’ve got Cats does Countdown, QI, Mock the Week etc.

Britbox has all the series since the start, when Stephen Fry was presenting.

In any group, there’s always that one obnoxious bro, isn’t there?

Fair enough. I think us and everyone else on this thread can definitely agree on that last point, at the very least. 🫡

You fail to sell when you fail to timely implement desirable features. And you fail to prioritise properly when you disregard or misinterpret feedback.

None of this is better mitigated by subscription models.

This sounds almost identical to the script our former VP of PM parroted. Everyone in engineering was vehemently opposed. But the C suite loved it, so we switched to a subscription model. Guess what, NEMs and govt clients don’t like paying subscriptions. No one does, but these are huge, powerful business entities we’re talking about here. You can’t force their hand. We lost 3 of our 4 biggest clients within 6 months. It took a massive amount of work to reverse course.

Just admit it. Subscriptions are nothing more than a blatant money grab. We (the SW industry) have been successfully releasing software and making fucktonnes of money for decades before some bean counter decided to get too greedy and come up with this bullshit.

they actually need to be able to consistently make pretty sizeable upgrades

Precisely! It keeps them honest. Furthermore, it forces closing the feedback loop with users. Developers need to understand what features users want most, and what bugs or usability issues need to be prioritised. Not listening to feedback means no future revenue, simple as that.

The subscription model does none of that. It’s just a greedy money-grab.

There’s actually quite a lot of software that monetises similarly to what you’re proposing. DxO and Ableton, just off the top of my head. Millions of happy users between those 2.

You get minor version updates for “free” (included in the one-time purchase). Upgrades to the next major version are discounted. Don’t need the features in the next major version? Stick with what you have for however long it works for you.

It’s by far my favourite model because it allows the developers to get paid, whilst not squeezing my neck. Everyone’s happy.

This is sage advice. Over the years I’ve come to realise that even a mediocre local roaster is always much, much better than anything from Starcunts or any of the other shitty retail beans.

That’s a useful thing to know, thanks!

Yeah, agreed. This whole “challenges” thing they like in America is bullshit. It’s just another distraction, it adds complexity and, like you said, would add even more time in the decision making. Just invest in improving refereeing ffs.

I have no experience with Jellyseer, but, in Sonarr, the Specials are unmonitored by default. You could try Monitoring them from Sonarr and theyll eventually show up in your library if you’re lucky (specials are usually harder to find than regular episodes).

Doesn’t solve your Jellyseer problem, though. Might be worth logging a ticket with the developers I suppose.

On an unrelated note, love your content choice! Who is your favourite DI? Mine’s Mooney, although I’m quite fond of Neville as well.

Fuck this abomination.

I gifted a friend one for his birthday. He uses it when he goes on holiday, camping etc. He’s happy with it, it does what it says on the tin.

https://wego.here.com/ is decent

I’m shocked! Shocked, I tell you!!!

Because, in general, the dev and the code reviewer(s) can’t accurately predict the impact of the changes. It’s a consequence of having a massive and complex code base. Now, best practices say that they should have automation in place that runs before the pull request can be approved, that tests against regression and unintended consequences. But, far too often, these things are deprioritised by management because of the “ship it now, we’ll fix it later” mindset.

To put it more succinctly, infinite profit growth is the reason everything is shit.