When I saw this in the cinema upon release I thought it was a fairly flawed follow-up to The Dark Knight (2008). It was a very good film. But it was a bit long and had a villain whose motives were more vague and less believable than the Joker’s.

My experience wasn’t helped by seeing it in IMAX and being unable to hear the dialogue for most of the film (there wasn’t a problem, it’s just how Christopher Nolan likes his audio. Which is insane. And it’s the reason I don’t see new Nolan films in the cinema anymore).

Since then though it’s become one of my rewatched staples, and I’ve seen it another 6-8 times. Though my feelings for it remained the same. That it was great, but rather flawed and lagged in parts.

But I’ve just gotten back from seeing it in the cinema again. And I’ve walked away with an increased opinion of it. Firstly, it wasn’t in IMAX, so I could hear basically every word.

But more than that it was just wonderful seeing a proper high-quality blockbuster in the cinema. The cinematography, soundtrack, sound design, and action were great to see on the big screen. Aside from Civil War (2024), I haven’t had a cinema experience come close to it for quite a few years. Sure, there’s some cringy moments – especially from Anne Hathaway’s Catwoman. And it remains a flawed film. But it’s still a Nolan film, so it’s many times better than nearly all the dross that I see these days.

The Dark Knight Rises is still a wonderful film to sit back and experience. 83%

Find out where to stream it. This review is also on Letterboxd. See my original review from 2012.

I’m 32. So hopefully death is still many decades away. But I still really need to document how I want my family to handle my digital legacy. Especially my websites. I don’t care if my personal files on my Mac disappear. But I’d like my websites to remain online for as long as possible after I die.

Right now I have three sites powered by Hugo and hosted on AWS. They should remain up for a decade or two as long as the $5/mo bill is paid. My biggest concern would be AWS introducing a new login or payment system that requires manually migrating to. A non-techy family member might struggle with that.

I also have my Micro.blog blog. As of today it doesn’t hate enough posts for me to be upset at the prospect of it disappearing. But if I did want to preserve it my main concern would be that Micro.blog could very easily be shut down. Luckily it’s all static pages and is Hugo again behind the scenes, so it shouldn’t be too tricky for a somewhat tech savvy friend/family member to get a copy of it all onto AWS.

My main concern are my Obsidian notes that get turnt into Learnt.me. In many ways that site is the most in-depth digital representation of who I am, so I’d like it to survive after I died. It’s turned into a website via Obsidian’s ‘Publish’ feature. But the site seems very JavaScript-y and not the easiest to have backups of. Luckily all the notes that the site are based on are just Markdown notes. And there’s also at least one other service that offers something like Obsidian Publish. But either way, worse case scenario all my notes could just be uploaded to an Apache web server and be browsed and viewed via the folder hierarchy. However I really like how Learnt.me looks and works. It would be a shame to lose that.

I’m not sure what the best solution is long term. I thought about having all the content hosted on NearlyFreeSpeech. It’s pay as you go, so I could deposit a bunch of money into it. But to be honest, as long as I can find a way for the AWS bill to be paid, that would be the easiest and most reliable route for long term hosting.

But either way, my digital ‘estate’ is in a much more stable long term state than it has been in the past. Sure, I have too many sites, which makes things more tricky. But at least none are powered by WordPress, which would make things very brittle and tough to keep up and running.