Can we define “expense”? I consider the loss of public lands extremely expensive. As well as the care and feeding of the carbon based plants required to operate so the base load is maintained. I don’t know numbers, but wouldn’t such an expanse of new solar install demand huge maintenace costs - in areas increasingly prone to natural disaster?

Sorry, but I’m curious about a few statements here. In what way is a reactor obsolete? And how does whatever degree of obsolescence compare with solar grids that are still undergoing massive innovation- isn’t anything we build today obsolete tomorrow? Do SMRs really take 20+ years to build?

Nuclear waste “issue” must be compared to electronic waste “issue” - with total cost of ownership calcs of rare earth mining and discarding batteries on a regular basis.

And yes, of that doesn’t address the main concern which is grid integration and base load sustainment.

So I guess we’re not going to do the smart thing, going nuclear, and instead landscape more of the country.

Sooooomebody once told me
That others were discussing
That some other people heard it from heads…

Of a handful of teams
Who maybe had believed
A stitched-together headline on X

Ive been extremely happy with jellyfin on my Roku 4K stick. Quite fond of it, overall. But for jellyfin the only issue I’ve ever come across was with a maaaaasssive 4K file that saturated my WiFi. I downscaled it a little and back to perfect.

I’m still learning myself, but I think in a good number of uses cases it qualifies. There are two parts of that explicit definition which seem important, “temporary” and “non-installation”. “Temporary” is the most ambiguous. An array of JBoD storing media files, which can be unplugged really at any time without affecting any system, meets that definition. Game installs or the operating system, less so. I totally get my specific usage may not lend to generic advice. In the interest of me learning, here’s where I started (which advises /mnt): https://perfectmediaserver.com/02-tech-stack/mergerfs/

I’m coming more from a server perspective but, fundamentally, all HDDs are “temporary”. Eventually that data might be in a bigger/faster/functioning replacement - so it’s best to treat the drive as something which can always be replaced.

Continuing that, you might mount to /mnt and then symlink that where you really want it, say …/games. That layer of abstraction allows you to replace the drive without much effect on install. Also allows for expansion via something like mergerfs (*no idea if that’s a good idea for your use cases)