DrinkyBird

KDE has the newer QML-based Kirigami and older Qt Widgets frameworks that are not consistent. Widgets apps absolutely look like actual desktop apps (menus, toolbars, dialogs), Kirigami apps look like mobile apps (nav bars, hamburger menus, page-based navigation). There is definitely a visual and functional inconsistency between the two, even if they use the same theme pretty well.

1. The UK and EU are rather large markets that they don’t want to miss out on.

2. There are software engineers in the UK and EU.

3. This specific implementation by Apple is not actually required by any UK or EU law, to my knowledge.

4. This specifically is or will be required by the laws of some US states and other countries.

Because some of us actually enjoy programming. For some people those side projects aren't about the destination, but the journey of learning how something works by making it with your bare hands.

It’s funny because the first AI scraper I remember blocking was from OpenAI’s, as it got stuck in a loop somehow and was impacting the performance of a wiki I run. All to violate every clause of the CC BY-NC-SA license of the content it was scraping :)

Go play the original Quake (not QuakeWorld) online and you will soon realise why games realised that concept was flawed as soon as it was implemented.

It works fine for LAN but as soon as the connection is further than inside your house, it’s utterly horrible.

Mercurial has no distinction between a bare repo and a non-bare repo: any repo can have a working copy or not. You can check out a working copy with `hg update somerevision`, or get rid of it with `hg update null`.

You can push to a repo with a working copy, if you like; nothing will happen to that working copy unless you run `hg update`. Since you don’t need a working copy on the server’s repo, you never run `hg update` on it, and it’s effectively what git calls a bare repository.

Perhaps they could ask Copilot to help them get IPv6 working.

It's the lack of subpixel anti-aliasing (aka ClearType). For some reason it's being erased from a lot of modern software. It's why Windows >= 8 UWP apps and GNOME look so blurry.

> It just works without any faffing around as Windows, MacOS, etc has done since the mid 1990's.

Unless you like your applications to save your window positions. I like Firefox to be on my left monitor, and if I use Wayland I have to manually drag it there every time I start it, because Wayland, in the year 2025, still lacks this basic feature that Windows, macOS, and X11 have had for like 40 years now.

(unless I use XWayland, which magically returns all of the missing functionality, though with a tendency to break other things)

The topics[0] feature in the evolution extension is probably even closer to Git branches, since they are completely mutable and needn't be a permanent part of your repo. Bookmarks are just pointers to changesets, and although that's technically how Git branches work, it's not how they work in practice in Mercurial because of its focus on immutability (and because hg and git work differently).

[0]: https://www.mercurial-scm.org/doc/evolution/tutorials/topic-...

Modern Mercurial with evolution is extremely pleasant, and the more I use it the more I abhor git whenever I have to go back to it. That plus Heptapod (fork of GitLab with Mercurial support) — it’s very nice indeed. I count myself lucky to mainly contribute to a project where we use all of this.

It’s a shame there’s still nothing quite like GitHub for Mercurial (anymore), where anyone can just sign up and create repositories. Heptapod has a public instance for FOSS, but it requires approval to create projects. There’s also a separate hosted instance for basically anything, but it’s commercial and costs money. One can also self-host, but GitLab is not exactly lightweight, and other solutions aren’t as integrated with evolution features.

You jest, but… https://mercurial-scm.org/help/topics/rust#rhg

I decided to just stay with Firefox and disable any rubbish that Mozilla adds as it comes.

I tried Librewolf, but the unstable RPM repository was very annoying, because zypper disallows system updates if even one repository fails to refresh. I also had some weird issues keeping it pinned to my desktop environment's dock. It also didn't want to save its window geometry (very annoying for me), and the only way to transfer from Firefox is to manually copy your profile data.

But mainly, I'm still dependant on Mozilla no matter where I go. They are the ones actually doing the hard work of developing the browser engine; all of these forks are just some patches upon that, so with Firefox I only have to deal with (and trust) Mozilla and my distro, and not some other project in addition to Mozilla.

The Met Office has WOW: https://wow.metoffice.gov.uk/support