On Android it’s more difficult, partially because it’s kind of like Windows where Google/Microsoft uses 50 separate reimplementations of Material/Fluent and there’s no consistency to be found anywhere.
4,281 karma · joined July 3, 2023
https://www.wells.dev/
On Android it’s more difficult, partially because it’s kind of like Windows where Google/Microsoft uses 50 separate reimplementations of Material/Fluent and there’s no consistency to be found anywhere.
It’s kind of like the difference between VS Code and MS Teams. Same company, same underlying technology (Electron), but Code is good while Teams is awful because MS invests so much more in Code. Even so, Teams-type apps are what tends to come to mind when people think of Electron apps because those are so much more common.
There are variances between Apple’s apps but they’re all using some combination of UIKit and SwiftUI regardless which limits how “wrong” they can be.
It has a few upsides that don't get written about often, compared to other monitors:
- Apple is extremely picky about panel QC, making things like dead pixels and patchy backlights much less common
- Its design practically eliminates the backlight bleed that's common with other monitors due to variances in bezel/panel fastener tightness
- No coil whine (surprisingly common even in other high end monitors)
- Some of the best glossy antiglare treatment I've seen, without the "gritty" coating that can cause a "sparkle" effect that's common on Dell monitors
- It wakes up and displays a picture almost instantly
It's not perfect and I'd prefer better specs for the money, but it's not a bad monitor. I've tested models that are more expensive than the Studio Display that fail to check some of these boxes.
The only problem is that it’s read-only. If QuickLook extensions could provide write capabilities too, you’d have 90% of a document centric setup.
For instance, while the person who never moved from their hometown might’ve been able to hit societal goalposts earlier on, they may never have had the opportunity to explore, experiment, and figure themselves and what they want to do out (as opposed to the identity they’d picked up via osmosis from family).
Speaking personally, in retrospect I was certainly underdeveloped in that way until my late 20s and early 30s, even though I couldn’t perceive that at the time. The requisite independence/autonomy and experience just wasn’t there until several years later. Had I locked myself into my situation with a marriage and children at that age I think it’s quite likely I would’ve come to regret it in the years following, increasing risk of outcomes such as divorce.
For instance, take function definitions. By just adding types to the function's arguments, you're potentially saving the reader a ton of time and mental overhead since they don't have to chase down the right the chain of function calls to figure out what it is exactly (or is supposed to be) that's getting passed in.
I’m in the latter camp and it’s exceptionally rare that major OS updates break anything for me.
It probably has more to do with how tiling with no margins with rounded window corners looks kinda awkward and entirely obscures the desktop, which is a bit more of a pillar UI element on macOS than it is on Windows and Windows-analogue DEs.
They're likely doing something funky to implement its shortcuts because the standard way wouldn't work everywhere in the app.
Ironically, at this point the cleanest implementation of Apple Music might actually be the Windows version, which as far as I can tell is a fresh codebase written exclusively in WinUI/WinAppSDK. Many hoped that the transition from iTunes → Music.app would turn out to be a blank-slate AppKit rewrite on macOS but that's not what we got.
Yes it's not free, but it's a cheap one-time purchase and I've been using the same license for a decade now, so it's close enough to free that the difference is moot.
I know some people are tired of all the prompts but I don’t think apps should be able to change those associations without first prompting the user.
That said, there should probably be a checkbox in system settings to disable login “prewarming”.
The problem with using game engines for UI is that their accessibility (support for screen readers, for example) is bad and they don’t adapt to the user’s desktop settings (e.g. light/dark mode and font size) unless you implement that yourself.
- Qt Widgets has a selection of controls that falls a bit short of that of AppKit and doesn't receive much attention any more
- Qt Quick/QML seems more mobile-oriented and web-styled, being barebones if you don't pull in a library of third party widgets (e.g. Kirigami)
- Neither go as deep as AppKit with functionality and require more third party library usage
- Practically speaking, developers are limited to C++ or Python for Widgets and JavaScript for QML
- Distribution of Qt apps is messy and error-prone
These aren't really dealbreakers on their own but pile up to pull the overall experience down.
With AppKit, one can build just about any kind of app imaginable by importing a handful of stock frameworks. The need to use third party libraries is the lowest I've seen on any platform, with many apps not needing any at all. That's huge for lowering the amount of activation energy and friction involved in building things, as well as for reducing ongoing maintenance burden (no fear of the developer of libfoo suddenly disappearing, requiring you to chase down the next best fork or to fork it yourself).
The other thing is not being afraid of opinionated design choices, which is also a quality of AppKit. This is going to chafe some developers, but I see it as a necessary evil because it's what allows frameworks to have "happy paths" for any given task that are well-supported, thoroughly tested, and most importantly work as expected.
GTK and Qt are probably the closest to this ideal but aren't quite there.
I just wish laptops had that layout as an option. It’d be particularly nice on ultralights like the ThinkPad X1 Nano or discontinued 12” MacBook.
This is what fuels a lot of my tab hoarding. Tabs are quicker/easier to clean up. This has led some browsers (like Arc) to blend tabs and bookmarks into the same thing, but I’m not sure how that this is the right approach either.
I’d like to explore bookmark manager design/UX in a project of my own at some point. It’s not something that’s gotten much attention in browsers in something like a couple of decades, and while plenty of external managers are out there none I’ve seen really nail it IMO.