RIP

Oh no, it’s worse than I thought, you must be blind then. (Folks with red-green color blindness would see a 17 in that picture.)

:P

So, quick quiz question: What number do you see in this picture?

Personally, I like it as an example here, because yes, technically you can’t know for sure that a fish feels pain, much like you can’t know for sure that a cat feels empathy, but it’s illogical to assume that if we don’t know about it that it doesn’t have it. The base assumption should be that these animals are similar to us, because they’re really not that different from us.
In particular, pain and empathy are crucial to survival for us. It would be extraordinary, if fish and cats survived without any notion of it.

(they anatomically can not have empathy)

You got a source on that? Not to be rude, but it sounds like the nonsense that meat eaters in denial tell each other like “fish can’t feel pain”, even though when you poke a fish, it obviously reacts to that.

I have a web music player that I’ve developed, and while it was never really intended to be used by others, I thought I had generally followed accessibility best practices. After using it for about two years, I realized that I never even implemented keyboard shortcuts. 🫠

Which is to say, one shouldn’t assume devs to know what they’re doing. At some point, I’m also just a user and I use software like everyone else does, meaning I pick out a path that works for me and then I hardly look left and right from there.
Features not being tested when you don’t use them yourself, that happens with any feature. But it’s much worse for UI features, because those are difficult to automate tests for. And accessibility is in an even worse spot, because it necessarily opens up a separate path, which is going to be invisible to me as a user, so it gets covered by neither automated tests nor by me just using the software.

I have to go out of my way to test accessibility, which means I have to be aware that a change I’m making might introduce a regression. That’s genuinely how lots of amateur developers work, which is probably the best explanation why accessibility support is often so amateur-ish…

I don’t think that was entirely serious…

I think the main reason why Word is losing mindshare, is because it was designed for paper. The whole formatting system makes the assumption that there’s a fixed width and height into which your text and images fit. In reality, a phone screen is a lot narrower and a widescreen monitor a lot wider.

Markdown never made these assumptions. For the most part simply because plain text reflows to fill whatever space you give it. But there’s no way to position an image either, I imagine mostly for simplicity’s sake. It can look goofy at times, but it never looks broken.
That’s why I can write this comment on my phone and someone else can look at it on desktop and it’s perfectly readable in both scenarios.

Seems like it’s Apache-2.0, but original sudo is under ISC license, which is more permissive as far as I’m aware. Although Apache-2.0 is very much still considered “permissive”, too.

Yeah, I really don’t know about responsibly managed. The new owner might be better than Google, but it’s unlikely for Chrome to be bought by a charity. Ergo the new owner will want to make their money back and enshittify accordingly.

They changed CEOs just last year…

They provide like 99+% of the development work. You won’t easily replace that with volunteers.

Yeah, thought the same with vertical tabs already. It’s extremely cool that it’s there now for folks who want it, but if you have a strategy for putting tabs into multiple windows and then dealing with those windows appropriately, then there’s really no point in making it a vertical list for the handful of tabs per window you’ll likely have…

I close all windows at once via the Quit feature, then it re-opens all of them. You can trigger that from the menubar (press Alt to unhide it) in the “File” menu at the bottom.
You can also re-open a closed window from the “History” menu in that menubar.

These might also be available in the hamburger menu. I’ve got that hidden, so can’t check easily…

The problem is that no matter how ineffective you believe Mozilla to be, it’s simply fucking expensive to develop a modern web browser.

According to openhub.net, Chromium has 35 million lines of code, Firefox 32 million, the WebKit engine has 29 million. Compare that to the Linux kernel which has 36 million lines of code.

The Servo engine has 7 million and is not usable.

Ladybird has 757,140 lines of code. There’s just no way that they don’t still need to develop manifold as much code as what they currently have, to support the features we expect from modern browsers. And they will need more money for that.

Yeah, Bethesda loves to ruin their game worlds with weirdly repetitive additions. Morrowind constantly spawns assassins on you, Oblivion does the Oblivion gates, Skyrim has the dragons. In the latter two, I think, it’s best to just not start the main quest, which prevents the Oblivion gates and dragons from appearing, at least if you replay the game.

renaming symbols, presenting documentation, formatting files,

Yes, these are supported via the Language Server Protocol (LSP). I’ve mostly been using it with the Rust LSP server (rust-analyzer) and well, it typically works, but sometimes you have to tell it to restart the LSP server and stuff (which isn’t a huge ordeal, but don’t expect everything to always work as well as in a full-fledged IDE).
I believe, for formatting, there’s also some non-LSP support.

showing code diagnostics beyond syntax errors (for example code smells or so),

This is supported in principle via LSP, too, but it depends on the specific LSP server, how much info it provides. The Rust compiler gives out relatively much on its own, which is passed on by the LSP server, but you can apparently also configure it to use the linter on save.

have AI integration (explain this, rewrite this, replace this with prompt output, …),

Not out of the box. There’s a way to define “External Tools”, which basically allows you to run commands and pass arguments to them and then use their output. For example, you should be able to define an External Tool, where you can select some text, then press your keyboard shortcut for that tool, so it sends the selected text to that tool and then it takes the command output and inserts it instead of the selected text.
While this is a powerful concept, I don’t know, if you hit limitations at some point.

specific framework integrations (reactjs, django, actix, …),

Nope, except where this might be covered by LSP. But there’s no obvious way to just install additional plugins, for example. You get about thirty built-in plugins and that’s it.

and stuff like expanding macros in C/C++ and Rust?

Well, expanding macros is also possible with the Rust LSP server. Don’t know about other languages.

openSUSE has the best integration of KDE, but I wouldn’t expect to see issues like yours on any distro, really…

That’s not the actual title of the article…

Yeah, good point. It also doesn’t update when the content of a file changes. So, in order to detect a change in a directory, you have to walk all the files and sub-directories and the directory itself to get the last-modified timestamp for each of them. Then determine the highest last-modified and compare it to what you measured in a previous run. If they differ, a change happened.