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.
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."
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.
I'm a Debian fan, and even I think it's absolutely preferable that app developers publish a Flatpak over the mildly janky mess of adding a new APT source. (It used to be simple and beautiful, just stick a new file in APT sources. Now Debian insists we add the GPG keys manually. Like cavemen.)
First of all, I already have Game Pass, so you don't get any new sales.Second, if I open the settings app in Windows 11, it just straight up crashes. (Can access the other tabs, e.g. through desktop customisation. But if I go to the front page, it crashes.)
It was broken by the update that supposedly added some other ads. But I've not seen them! I had to disable the "recommendations" in start menu because it made the start menu not work at all (due to the aforementioned crash, same deal).
This actually really sucks, though. Windows Store apps do not update themselves, Xbox services stopped working (due to being unable to update WS games), and I don't know if Windows Update works or not. I guess I need to reinstall when I get arsed to.
Up to 2.x, GNOME used what was basically the MacOS philosophy: make things easy and simple and intuitive, but if the user wants finer control and power features, make sure it's still possible somehow. GNOME 3 and later pretty much adopted the philosophy that there's the GNOME path of simplicity and streamlining, and power user functionality is going to be removed from the core and relegated to extensions. And, of course, GNOME started requiring boatloads of memory to run, which to me didn't go hand in hand with "simplicity".
I eventually settled on using XFCE, because it didn't have the bloat and still had enough customisability. Really good environment for old and underperforming systems. If I'm using a modern high performance system, I'm actually pretty impressed by what KDE Plasma is doing these days.
GNOME 1 & 2: The dock is in the bottom by default. It can be moved elsewhere if the user prefers it.
GNOME 3+: The dock is wherever we think the user is likely to find it. Maybe it's in the bottom. Maybe it's nowhere. Maybe it's everywhere. Verily, who can even begin to understand the mysteries of the brain?
Debian's Firefox is Firefox ESR, or Extended Support Release. It's behind the bleeding edge, but gets security updates.
If you want the bleeding edge Firefox, you can add Mozilla's own APT repository and install it. Doesn't even conflict with Debian (firefox-esr vs firefox, it even uses a separate user profile by default). Instructions are on the Firefox download page somewhere.
I mean, C is a high level language? Now, sure, C isn't a super expressive language and every C statement compiles to very few assembly instructions comparatively speaking, but it has a whole lot of stuff that assembly doesn't have. Like nice loops and other control structures and such, and not worry about which processor registers are used.
There's still a few sites I deploy changes to using ssh+rsync. ...which is made considerably easier by the fact that it's just a static website generated with Jekyll.
Ah, but readable by whom? I have a bar code font here. If you can't read it you're clearly not nerd enough.
Also, putting the Ten Commandments in classrooms will only turn the kids into sarcastic, blasphemous little fellows. ...I mean, more so than they already are.
Not exactly boned but it probably doesn't make practical difference to store "local time + tzinfo timezone" than just UTC time.
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.