If I have two PDF viewers, should both be called "PDF viewer"? Gnome seems to love hiding the actual names (the gnome document viewer is actually called evince).

View it this way. If I’m a new user to Linux, KDE tends to come with far more apps than GNOME, with names that are often so opaque every app is a mystery. And not in a good way.

“Oh… I thought Konquerer might be a video game, involving Conkers.”

You nailed it: GNOME targets new users. KDE doesn't. The advantage of having unique names is that you can actually talk about them, and that includes finding documentation and solving problems via a search engine.

Try finding anythng useful when your query is based on a generic name, e.g. "document viewer crashes".

> Try finding anythng useful when your query is based on a generic name, e.g. "document viewer crashes".

Gets tragically hilarious when the document viewer program changed between release.

> GNOME targets new users.

Which is of course the correct strategy in the exploding-growth market of not only Linux Desktop, but desktop computing in general.

...wait a second...

If only in the menu there was a description of what it does, written perhaps just under the name… oh… wait! THERE IS!

What about having it listed with the actual name, but when you're viewing it in the program launcher you have a hint in gray? Something like this:

- Okular Document Viewer

This is roughly how it works now. Also, searching matches on its description.

Sounds good! I don't use either anymore so I wouldn't know.

Applications in every KDE system menu and search box result list have descriptors about what the application does that follow the application name. Didn't mean to be rude but it's honestly not hard to read the descriptor textsbefore clicking on something.

Nobody that would be confused by this would ever use Konqueror. Chrome or Firefox, those are the choices.

Why does it alternate between 2023 and 2013?

It's intentional. What's interesting 10 years ago is likely still interesting now.

What's interesting for ten years is likely really interesting. I often find a better selection of links on the third or fourth page of HN thanks to their algorithms, of stories that have held position for several days. Perhaps these are more evergreen topics than faster rising and falling front page submissions.

EDIT: There is a typo in the word "business".

Only if the content still exists after 10 years. There was a lot of noise back then too, but the irrelevant stuff has been forgotten!

See https://en.wikipedia.org/wiki/Lindy_effect

You say underpromotion, but something people are surprised by is making a second queen ime. People sometimes assume promotion is actually "taking a captured piece back".

Very understandable how this developed in the era of over the board play. You can't have two queens when they don't physically exist!

I always use an upside down rook, somehow there's always one available by then.

I end up using a checkers piece, since pretty much every board I've played on has them.

Indeed, we're being too kind to you.

Also at http://om-language.org

Hah, I thought I was the only one who lifts shift too late and gets :Wq.

> Technically, int32_t is bad in that way, but we are not fooled by it.

Meaning? On my system int32_t is directly typedefed to unsigned int, absolutely no hidden pointers or conversions.

int32_t promotes to long, converts to unsigned, and truncates to short and char, all silently.

I think the iBooks were made like that.

That’s correct and here’s a case modification where someone removed the white paint off the inside.

https://www.applefritter.com/hacks/tronbook

That applies to GLSL in general. I tried once to emulate that using C unions, but quickly realized that there's no solution for v.xz, v.xw, v.yw, etc.

You can write functions like xyz(v) and that works well enough. Even better if you have ufcs or methods.

That's such a perl/raku thing, and I mean it in the best way possible.