premysl

> it doesn't support wide gamut color

That's wrong, you declare this with an ICC profile, done.

Lossy WebP has an important limitation in being YUV 4:2:0. And it's strictly 8-bit. That is the actual reason it doesn't replace JPEG, which is rarely even implemented to a greater extent.

Lossless WebP replaces GIF. Despite much better compression, it doesn't replace PNG, which supports 16 bits, and has stronger metadata support.

When you familiarise yourself with macOS, you arrive at the conclusion that GNOME is indeed not a cheap copy of Mac, it is something worse: a miserable attempt at copying its ideas. There are many examples, but from the top of my head and clicking around:

- Window title bars - Menu bars: removed while copying macOS, but no global menu either. If only it was like macOS! - Symbolic icon craze - Autohiding a context menu after 0.5 seconds of holding the button (since GTK 3) - The top right area in GNOME's Hell - The "Apps" view in GNOME's Hell, which also has a Dock wannabe - Nautilus is basically Finder - Nowadays animations that you can't turn off

Most of the damage to GNOME has been done in version 3. I've converted away from anything GTK 4 because I can't stand it anymore.

Though I admit that it's cohesive and if you expect very little, it kind of works. Also there's probably nothing better for touch screens.

Talk to R1 for a while, and you'll notice that it's both censored and aligned.

I think the most free-minded large models might be the Groks, but just slightly, as they have different biases. In sum, there's strength in diversity.

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.

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.

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).

Few, if any, other mice are touchpads. The Magic Mouse is more of a touchpad that happens to be capable of being used as a mouse.

DLUs solve the wrong problem.

You actually want autolayout, so that different languages only need translations and otherwise don't need almost any extra work.

Linux has, I think, proved, that fixed window sizes are needless.

GObject signals and properties are very powerful. The layouting model is sane. In general, the toolkit is very regular.

It's hard to just give you a generic answer. I can only really compare to Win32, Cocoa, and some parts of the web stack.

Of course. It has almost no effect at all, as far as I can say. These are also important:

  defaults write com.apple.dock autohide-time-modifier -float 0.1
  defaults write -g NSUseAnimatedFocusRing -bool NO
  defaults write com.apple.dock springboard-show-duration -float 0
  defaults write com.apple.dock springboard-hide-duration -float 0
  defaults write com.apple.dock springboard-page-duration -float 0.1

> 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).

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.

From my experience, both Mastodon and Pleroma are massively overcomplicated resource hogs that are hard to set up, configure, or navigate.

Author here, this is implied from runtime dependencies, it's in generic packager speak.

Ideally, I would provide pre-built packages from CI, of course.