The Asciidoctor flavour of AsciiDoc doesn't have a specification. There is only a working group. The parsers are a mess composed of regular expressions.
There are in effect two different versions of AsciiDoc, because Asciidoctor people have appropriated the name while making their own changes to it and marking what they dislike as deprecated.
AsciiDoc cannot express all of DocBook, for example figures with multiple images.
While I despise Markdown, there isn't all that much to be a fanboy of. Just the syntax is overall saner.
> These damn animations man... they're so fluid and springy and easy to use in SwiftUI, that it lures you into adding them everywhere.
The constant animations are what makes me dread and despise working with Apple software. Each time something moves for no good reason whatsoever, I die inside a little. Every few seconds.
> [...] the same animation was driving me nuts because I was switching spaces so often, that the animation was slowing me down
Exactly. Props to the author for making them possible to turn off. The operating system at large still has _tons_ of them that you can't get rid of, but it's the thought that counts.
> Reacting to keyboard events is still something I do outside of SwiftUI
SwiftUI is a nice idea in principle, what with being reactive, but I found that I cannot achieve anything worthwhile without piercing down into the lower layer of AppKit. And then I asked myself why do this clownery in the first place.
Ultimately, trying to learn Apple frameworks has made me love GTK+, because it's so beautiful and elegant in comparison (disregarding that it's currently deeply broken on macOS).
People just expect things to be integrated. Even Wi-Fi is, although it's probably typically an M.2 card. I have a <2000 computer that had both integrated audio and video, and it's kind-of become a norm.
Integrated sound cards are way more susceptive to interference, though, and the quality suffers a bit. They're merely good enough.
Also, people generally seem to use USB sound cards, as it removes even more room for interference (though my ASUS Xonar Essence STX sounds great already, unlike the integrated solution that transfers power rail and other noise).
It should also be noted that in general, Xlib can do a lot more than XCB with a /lot/ less effort and bugs, and has an actual documentation, tutorials, books.
Xlib certainly is quirky, in particular around error handling, though.
The reliance on a phone seems terrible, I would never install a banking application unless sufficiently threatened. I prefer our (Czech) more-or-less direct bank transfers, for which I don't need to leave my web browser.
Ideally, I would provide pre-built packages from CI, of course.