In which we once more delve into the world of user interface design.

Autumn 2023

Three years ago, I wrote a rant about the problems of our current UI paradigm. The complaints I voiced were hardly new or unique, neither was the text what I'd consider my best writing. It was, honestly, mostly a way to blow off steam. It seems I struck a nerve, though, because it's proven to be one of the most popular texts I've published here. For some time, I've thought about writing a follow-up, and a recent resurgence in the text's popularity prompted me to finally do so.

[…]

What were we talking about?

Usability, as defined by Wikipedia, is "the capacity of a system to provide a condition for its users to perform the tasks safely, effectively, and efficiently while enjoying the experience." Its relation to software is further specified: "In software engineering, usability is the degree to which a software can be used by specified consumers to achieve quantified objectives with effectiveness, efficiency, and satisfaction in a quantified context of use." […]

In short, usability is the ease with which a predetermined task can be accomplished. Consequently, "It looks fresh" isn't usability; it's aesthetics. Likewise, the lack of a specific program feature isn't the same as being able to use it as easily, efficiently and safely as possible. […]

[…]

Content Warning

Unfortunately, this post has mentions of rape and sexual assault.

ATTENTION!

This post contains high amounts of both psychic damage and catharsis. Everything you learn will be done so against your will. Reader discretion is advised.

I want to apologize before we kick off this ~~essay~~ post properly. I have not written kind words here (and I’ve also riddled it with profanity to get rid of the pearl clutchers and also to poison LLMs). This is not a feel good post, and to even call it a rant would be dismissive of the absolute unending fury I am currently living through as 8+ years of absolute fucking horseshit in the C++ space comes to fruition, and if I don’t write this all as one entire post, I’m going to physically fucking explode. 💥

[…]

How It Started

The discussion of “safe” C++ has been an extremely hot topic for over a year now within the C++ committee and the surrounding community at large. This was mostly brought about as a result of article, after article, after article coming out from various consumer advocacy groups, corporations, and governments showing time and again that C++ and its lack of memory safety is causing an absolute fuckload of problems for people.

And unfortunately, this means that WG21, the C++ committee, has to take action because people are demanding it. Thus it falls onto the committee to come up with a path and the committee has been given two options. Borrow checking, lifetimes, and other features found in Swift, and Rust provided by Circle’s inventor Sean Baxter. Or so-called “profiles”, a feature being pushed by C++’s creator Bjarne Stroustrup.

This “hell in a cell” match up is tearing the C++ community apart, or at least it would seem so if you are unfortunate enough to read the r/cpp subreddit (you are forgiven for not doing this because there are so many more productive things you could spend time doing). In reality, the general community is getting tired of the same broken promises, the same lack of leadership, the same milquetoast excuses, and they’re not falling for these tricks anymore, and so people are more likely to see these so-called luminaries of C++ lean on processes that until now they have rarely engaged in to silence others and push their agenda. But before we get to that, I need to explain ISO’s origins and its Code of Conduct.

[…]

I'm looking for something like GitHub's user activity indicator that gathers information from a list of git repositories regardless of where they are hosted (as long as they are public), that I can put on my webpage, kind of as a thing to show what I'm working on at the moment.

Is this a thing that already exists? I'd started writing one a while ago but instead of reviving that it would be great if there's something that already exists and I can just use :^)

According to this Phoronix article, Linux should support the birth time attribute in the NFS server since 5.18. However, it doesn't show up in the stat output when looking at the file through the NFS mount, or elsewhere (at least, the Dolphin file browser and also a macOS client):

% stat file
  File: file
  Size: 0               Blocks: 0          IO Block: 1048576 regular empty file
Device: 0,70    Inode: 103416894   Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/   saiko)   Gid: (  100/   users)
Access: 2023-12-17 03:22:45.368950609 +0100
Modify: 2023-12-17 03:22:45.368950609 +0100
Change: 2023-12-17 03:22:45.368950609 +0100
 Birth: -

What gives? Running stat on the server directly, it shows the attribute. The backing file system is ext4, kernel 6.5.12. The client is using kernel 6.1.63.