Domino’s tries to keep their ingredients fairly similar globally, but Pizza Hut tries much more agressively to adapt to local tastes in certain markets—like Thailand. I don’t know who they poll, but thousand island sauce with imitation crabs is not where it is at, & the frozen dough sucks. At least Domino’s uses corn meal + a shit ton of garlic to mask being lower quality. That said, I had Pizza Hut in Hanoi on Christmas a few years ago & it was honestly was one of the best pizzas I had ever had—from the crust, to zesty sauce, to the right amount of burn on the cheese. So… 🤷

One day they will wake up & provide an OLED option with 100% DCI-P3

Movim is another web UX option (comes with posts + feeds that can easily be crawled as well so you don’t have everything stuck in the black hole of chat).

It is the exact opposite. Ligatures were created to help deal with the lack of clarity when symbols overlap. fi, ff, fl, ffi, have historically (like print press historical) been common ligatures where others are stylistic, where others are downright questionable & make things harder to read. The first category should almost always be supported, & the others can usually be disabled if not commonly off by default where you opt in for some design, not for general body copy.

What you are referring to about ‘programming ligatures’ is an outright abuse of open type features full of false positives, ambiguities, & lack of clarity for outsiders to understand what your code means. What you want is Unicode supported in your language so you can precisely what you mean than using ASCII abominations—like meaning → but typing ->, dash + greater, than which isn’t at all what you mean which is a rightward arrow. (with a non-exhaustive languages with decent Unicode support: Raku, Julia, Agda, PureScript, Haskell with Unicode pragma, & all APL dialects).

Best way to combat the issue in this example is to create zero Discord accounts & embrace open, encrypted communication options like XMPP & Mumble, etc.

Please correct me if am wrong since I have never made any mobile OS applications.

There’s the $100 fee or whatever to join the developer program even if your app is free. There is a slow manual review process. You have to share a 30% cut with Apple of any profit. Most of the tooling for iOS requires a macOS machine which is another massive money sink as well as being proprietary with no source available. I believe GPL or similarly licensed code isn’t allowed on the App Store either due to ToS conflicts.

Most privacy-friendly things take an source available, open source, free software, or other (post-open, copyfarleft) approach that conflicts with Apple’s model for software, but also developers are likely to be on Linux or BSD + a Linux or Android phone where everything will be more arduous to build & test while not even being a device they or their friends would use so why both building if likely you aren’t even getting paid for it.

If you are into tea, you might want to consider an electric kettle with variable temperature. Nothing is more of a shame than burning good leaves or having to be limited to leaves that can handle a near boil. It’s tricky & a futz to watch a thermometer for boiling water to a specific temperature for your tea—especially if you are relying on that cup to help your mood & concentration.

I would be furious if a different app that required Android or iOS to use became the norm. Have a Linux phone, a KaiOS phone, or no phone? Too bad.

NixOS, would like to try Guix

It’s not compatible with other Markdown forks, but the whole Markdown ecosystem is a mess duct taped together by more forks & extensions that aren’t compatible either. Even the common denominator CommonMark is feature-barren & isn’t suitable for documentation or technical writing, but boy howdy will the next guy have his Markdown contraption to sell you.

Two friends in college recommened it while I was sick of Windows bloat/tracking & setting up programming tools seemed a lot easier

Try WINE. Raise issue with devs. Or just decide not to use it.