Downvotes rewarded with hugs.

  • 16 Posts
  • 197 Comments
Joined 8 months ago
cake
Cake day: October 30th, 2023

help-circle









  • That was a really fun buildup and coda. The resolutions to the conflict with Sutekh and the mystery of Ruby’ mum were underwhelming, though. If you’re going to have the big bad simply be put on a leash and dragged through the time vortex, you better have a gut punch up your other sleeve. But they didn’t.

    The central conceit is fun but half-baked. Turns out after ages and ages riding the TARDIS, Sutekh had become a scoreboard fanboy like any mortal Whovian who’s been watching since 1975. Everything that happens to the Doctor has to make sense to him (maybe Ruby’s mum is the Rani?!) and he simply can’t kill off the Doctor or Ruby without learning who left her at the church, so he can continue building headcanon from there while the universe spins into entropy. This finale has really been about playing against viewer expectations but I didn’t expect it to be the basis of Sutekh’s defeat…

    So now we know Ruby’s mum was a nurse in Coventry all along. That is a nice reversal, of course, and plays into the Doctor’s conviction that everyone is special (see “Space babies,” among others). Good thing Sutekh is gone though, because he would be furious at this development… There’s no complex cosmic puzzle to be solved, Ruby’s birth and abandonment dovetails perfectly with real life statistics as Kate told us last episode.

    After a season of teasing Susan Foreman, I found the Doctor’s and Ruby’s talk outside the coffeeshop to be revealing. Trying to talk her out of reconnecting with her mum, he’s really talking about himself abandoning his granddaughter, and rationalising why he never went back for her. That is pretty damning if not for his admission to Kate in the last episode that he might bring disaster on Susan if he were to find her.

    I liked those thematic strands and the way they set up for next season, and the general storyline if this double feature finale —but the boss fight might have needed a bit more workshopping before making it to production…





  • I just made the move to another computer, using the same distro and DE setup as the old one. So far I managed by backing up ~/ and /usr/ so I could drop in system and programming settings.

    I don’t know how that will work if you’re going for a new distro but it’s always good to have your old configs for reference!








  • Same argument stands though. It’s not like LOS is a company with a ton of venture capital. Maintainers are the same randos from the same forums, they just banded together under a common flag. Some of the “official” LOS devs even release unofficial prereleases on other sites. And sometimes support drops because the maintainers may or may not have the physical device to test on.

    If you are running an unofficial rom made by some random on a forum, that’s on you.

    LOL you haven’t lived until you flashed a weird ROM off XDA-dev to realise it was developed for some regional variation of your device, the UI is all in a language you don’t read, and the developer customised the OS to their own niche use case that you’re not partial to.

    Mind, it used to be easier to casually flash ROMs (for me at least) back in the Jellybean/KitKat days. Fun times!


  • I’m fairly happy with LineageOS myself

    but there is so much false information about this OS, namely compatible phones that simply don’t work with this OS and no support.

    I think you’re overreacting a bit calling it “false information”. LOS is a FLOSS project that many individuals have ported to their device — and either at some point they buy a new phone and drop that development, or they realise what a massive project it is to maintain it. That’s just a general bummer with open source, especially when people volunteer their free time.