schizo

ArchiveBox is great.

I'm big into retro computing and general old electronics shit, and I archive everything I come across that's useful.

I just assume anything and everything on some old dude's blog about a 30 year old whatever is subject to vanishing at any moment, and if it was useful once, it'll be useful again later probably so fuck it, make a copy of everything.

Not like storage is expensive, anyway.

I got a CA-53 recently myself, for much the same reason.

Nobody ever said anything about my Apple Watch, but holy crap does everyone love a calculator watch.

(Which is hilarious because as a kid, I was teased as a nerd for having such a thing.)

It is mostly professional/office use where this make sense. I've implemented this (well, a similar thing that does the same thing) for clients that want versioning and compliance.

I've worked with/for a lot of places that keep everything because disks are cheap enough that they've decided it's better to have a copy of every git version than not have one and need it some day.

Or places that have compliance reasons to have to keep copies of every email, document, spreadsheet, picture and so on. You'll almost never touch "old" data, but you have to hold on to it for a decade somewhere.

It's basically cold storage that can immediately pull the data into a fast cache if/when someone needs the older data, but otherwise it just sits there forever on a slow drive.

Nobody thought it was possible, says man who led project because he thought he could make it possible.

Also, this looks like quantum entanglement which is a thing that's hardly a new concept and/or considered impossible, so uh, dude needs to get out of clickbait mode and ship a working example instead.

Well, I fully expect him to step on his dick, but I did not expect him to also kick himself in the balls while doing so.

Congrats Matt, rarely are my expectations of dumb behavior exceeded so spectacularly!

Here's a crazy idea: make the CAPTCHAs so complicated humans can't complete them.

That way if someone does, you know they're a bot.

I should probably patent that or something. (Is joke, etc.)

...depends what your use pattern is, but I doubt you'd enjoy it.

The problem is the cached data will be fast, but the uncached will, well, be on a hard drive.

If you have enough cached space to keep your OS and your used data on it, it's great, but if you have enough disk space to keep your OS and used data on it, why are you doing this in the first place?

If you don't have enough cache drive to keep your commonly used data on it, then it's going to absolutely perform worse than just buying another SSD.

So I guess if this is 'I keep my whole steam library installed, but only play 3 games at a time' kinda usecase, it'll probably work fine.

For everything else, eh, I probably wouldn't.

Edit: a good usecase for this is more the 'I have 800TB of data, but 99% of it is historical and the daily working set of it is just a couple hundred gigs' on a NAS type thing.

I'll admit to having no opinion on windowing systems.

If the distro ships with X, I use X, and if it ships with Wayland, I use Wayland.

I'd honestly probably not be able tell you which systems I've been using use one or the other, and that's a good thing: if you can't tell, then it probably doesn't matter anymore.

I'm disappointed in that writer.

Better phrasing: Sega started as a rock'n'roll breath of fresh air that did what Nintendon't.

Perhaps it's just me, but they've been releasing a good number of actually good things, though?

Persona, Yakuza, PSO, and even the fact the Sonic movies were..... good? Or at least entertaining enough, which is a victory for a video game movie series, heh.

I'm not up on corpo shareholder suits in general, but has there been a high-profile case of shareholders demanding the return of salary from CEOs that managed do nothing useful?

Like, did Carly or Leo have to pay HP back for their blunders? Or Marissa at Yahoo? And so on, etc.

One thing you probably need to figure out first: how are the dgpu and igpu connected to each other, and then which ports are connected to which gpu.

Everyone does funky shit with this, and you'll sometimes have dgpus that require the igpu to do anything, or cases where the internal panel is only hooked up to the igpu (or only the dgpu), and the hdmi and display port and so on can be any damn thing.

So uh, before you get too deep in planning what gets which gpu, you probably need to see if the outputs you need support what you want to do.