umbraroze

The way I think it, it's possible a really small number of GPUs would be enough to render the framebuffer, you'd just need an army of low-power graphics units to receive the data and render it on screens.

Having a high-power GPU for every screen is definitely a loss unless the render job is distributed really well and there's also people around to admire the results at the distance where the pixel differences no longer matter. Which is to say, not here.

Back in 1997 I was like "Ooh, Debian is mildly easy to install (compared to Slackware). Just need to engage my brain a few times maybe."

(The first Slackware guide I read in 1996 had an ominous warning about getting the ModeLines right in XFree86 or the monitor will catch fire. This, fortunately, was a little bit of exaggeration. Over/under refresh frequency protection was already a thing.)

Now? "Oh no I fucked up my password shit and can't login. I'll need 5 more minutes to completely reinstall this Raspberry Pi image. I should have engaged my brain!"

Shit, we've gotten to the point that your average desk jockey can probably install freaking FreeBSD on the first try. If that's not a good sign I don't know what is.

Not exactly boned but it probably doesn't make practical difference to store "local time + tzinfo timezone" than just UTC time.

• You record an event occurring at local time
• You store it as UTC
• Local time zone definition changes
• Well whoop de loo, now you need to go through tzinfo to make sense of the past data anyway rather than relying on a known offset

Even if you store everything in UTC, you may be safe... but figuring out the local time is still convoluted and involves a trip through tzinfo.

DAM as in digital asset management. Fancy word for "image library organiser".

Oh, everything works with Affinity. Thing is, Adobe is pretty much the only software ecosystem that is subtly (or not so subtly) making people think inwards. "I'd love to try that piece of software, but if it's not running as a Photoshop/Lightroom plug in, is it even worth trying?" Whereas when people who use other software are more likely to go "Well my favourite software package doesn't do thing X, but I have this other piece of software that does that, it's not even a hassle."

Also, when I switched from digiKam to ACDSee, at no point did I have to go "but what about my Adobe-locked-in catalogue, oh no!"...

I think it's only a good thing they're not trying to shoehorn DAM features into their existing apps. If they made a DAM software it'd have to be an external app anyway.

I did perfectly fine with digiKam in the past, and nowadays I'm perfectly happy with ACDSee. ACDSee even shows thumbnails for Affinity Photo project files.

Well, the whole point of NaNoWriMo is to produce a viable first draft. Some of these are so far removed from final draft it's not even funny. None of these drafts are good enough to be accepted by editors at publishing houses, sadly. ...No matter if we're operating in the ideal sphere of literary merit or the actual crass sphere of marketability publishers respect.

I'm currently struggling with my literary projects. I can whomp out a 50,000 word novel every November in NaNoWriMo, no sweat.... but it's been over a decade now and I really need to get to editing at some point. Shit.

Reminds me of a random quip about how American universities are real estate holding companies with sports team subsidiaries that also, on occasion, also award academic degrees.

Not "auto trust", of course, but rather make adding keys is a bit smoother. As in "OK, there's this key on the web site with this weird short hex cookie. Enter this simple command to add the key. Make sure signature it spits out is the same on the web page. If it matches, hit Yes."

And maybe this could be baked somehow to the whole APT source adding process. "To add the source to APT, use apt-source-addinate https://deb.example.com/thingamabob.apt. Make sure the key displayed is 0x123456789ABC by Thingamabob Team with received key signature 0xCBA9876654321."

I remember the Internet of 1999. It was full of awesome weirdos. Everyone thought it was great that awesome weirdos had a place to say what they want to say.

If anything, in some senses, the Internet of 1999 was far more diverse and inclusive than the Internet of today.

Hey now, you just can't call him "Benny" out of the blue. His birth name was Benjamin. That's what he should be called. That's exactly according to his own rules he's espousing. /very sarcastic of course

Just today I heard someone whining about how in LinkedIn and other recruitment sites there's like five bazillion profile tag options for RDMBSes and various dialects of SQL... when in actuality the recruiters are probably only concerned if the developer can do a bloody SELECT and stuff.