![](https://lemmy.ananace.dev/pictrs/image/49af6b34-655f-42a6-9854-e2cb3ae15fd6.png)
![](https://beehaw.org/pictrs/image/fed50129-04e7-4dbc-8f54-4ba5bae58370.png)
It releases while I’m on the way back home from a trip to Manchester, might have to bring my Deck so I can play on the flight/train.
Just another Swedish programming sysadmin person.
Coffee is always the answer.
And beware my spaghet.
It releases while I’m on the way back home from a trip to Manchester, might have to bring my Deck so I can play on the flight/train.
Seems to work with my personal setup at least, with two libraries - the default on ~/.local/share/steam
, and one on /mnt/storage/steam
- and Stardew Valley installed in the secondary storage library
Factorio is great, I’m also a fan of X4.
Going to be really amazing to play Factorio again without knowing how to solve everything.
In general, browser benchmarks seem to often favor Firefox in terms of startup and first interaction timings, and often favor Chrome when it comes to crunching large amounts of data through JavaScript.
I.e. for pages which use small amounts of JavaScript, but call into it quickly after loading, Firefox tends to come out on top. But for pages which load lots of JavaScript and then run it constantly, Chrome tends to come out on top.
We’re usually talking milliseconds-level of difference here though. So if you’re using a mobile browser or a low-power laptop, then the difference is often not measurable at all, unless the page is specifically optimized for one or the other.
There’s a bunch of extensions that allow you to switch user-agent easily, I personally use this one, it includes a list of known strings to choose between as well.
They used to also use the unreleased version 0 of shadow DOM for building the Polymer UI, which - being a Chrome-only prototype - understandably didn’t work on Firefox, and therefore instead used a really slow Javascript polyfill to render its UI.
I haven’t checked on it lately, but I imagine they must’ve changed at least that by now.
One thing you can test is to apply a Chrome user-agent on Firefox when visiting YouTube. In my personal experience that actually noticeably improves the situation.
Well, things like the fact that snap is supposed to be a distro-agnostic packaging method despite being only truly supported on Ubuntu is annoying. The fact that its locked to the Canonical store is annoying. The fact that it requires a system daemon to function is annoying.
My main gripes with it stem from my job though, since at the university where I work snap has been an absolute travesty;
It overflows the mount table on multi-user systems.
It slows down startup a ridiculous amount even if barely any snaps are installed.
It can’t run user applications if your home drive is mounted over NFS with safe mount options.
It has no way to disable automatic updates during change critical times - like exams.
There’s plenty more issues we’ve had with it, but those are the main ones that keep causing us issues.
Notably Flatpak doesn’t have any of the listed issues, and it also supports both shared installations as well as internal repos, where we can put licensed or bulky software for courses - something which snap can’t support due to the centralized store design.
Especially if you - like Microsoft - consider “Unicode” to mean UTF-16 (or UCS-2) with a BOM.
Do you have WebP support disabled in your browser?
(Wasn’t aware my pict-rs was set to transcode to it, going to have to fix that)
I’m currently sitting with an Aura 15 Gen 2, and I’m definitely happy with it.
I do wish they’d get their firmware onto LVFS, but that’s about my main complaint.
Been using the KeyDB fork for ages anyway, mainly because it supports running in a multi-master / active-active setup, so it scales and clusters without the ridiculousness that is HA Redis.
Version requirements? No rules!
He won’t be allowed to perform at Eurovision with the Windows 95 name/trademark/logo, so it would be hilarious if he switches to a name like Linuxman during it.
This looks really odd in relation to other fediverse software; Why /magic
and required to be on the root of the domain? Why hard-require routing the domain part of the user ID when .well-known/webfinger
exists? Why is there a X-Open-Web-Auth
header which the spec only describes as “its purpose is unclear from the code”?
So many questions.
I definitely like the idea of distributed sign-in, Solid did a decent work of that many years ago after all. This particular proposal just looks rather odd.
Here’s a .jxl
JPEG-XL upload I did on Lemmy three days ago;
https://lemmy.ananace.dev/pictrs/image/ad4e745e-0135-4cc3-889c-052600828d82.jxl
The built-in Firefox support is only activated for unstable builds, so you can’t enable it on stable unless you manually enable it during compile-time.
It’s reasonably easy to guess exactly what you paid for the game, since the only change in price since launch was a $5 bump in January last year. It’s never been on sale.