HNHacker News
TopNewBestAskShowJobs

jwells89

4,281 karma · joined July 3, 2023

An iOS/macOS dev and tinkerer with an interest in UI design.

https://www.wells.dev/

submissionscomments
jwells89··on We're forking Flutter
It’s more difficult to distinguish if an app is Flutter or some other cross platform framework, but “native or not” is very easy on iOS. Even React Native, which is the least foreign, has tells.

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.

jwells89··on We're forking Flutter
Not all non-native-looking apps are badly implemented, but a huge number of apps that use cross-platform frameworks do so primarily as a means to cut costs because the goal is to make development as cheap as possible, and that shows in other aspects of these apps too. This creates an association between cheap/lazy apps and cross platform UI frameworks.

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.

jwells89··on We're forking Flutter
The two things that stick out the most to me are navigation behavior and text fields. Cross platform frameworks seldom get either right, with react native being particularly bad on the navigation front.

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.

jwells89··on New iMac with M4
Of course, but those cables (or more likely, just one cable) can be stashed away in a drawer 99% of the time. The bundled keyboard and mouse/trackpad can go months between recharges, especially with lighter less frequent use that something like a living room or kitchen machine might see.
jwells89··on New iMac with M4
The Samsung model has a well-known issue with severe coil whine. Not a dealbreaker for everybody but worth taking into account.
jwells89··on New iMac with M4
I'm happy with mine too.

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.

jwells89··on New iMac with M4
Low number of cables has also been one of the points of appeal for the iMac, to the point that it was a focal point of marketing for the original model. For the average person's setup the current model only needs a power cable.
jwells89··on Building Document-Centric, CRDT-Native Editors
In my mind, QuickLook on macOS is probably the closest thing we have to document-centrism in a modern mainstream OS, with how the OS discovers QuickLook extensions in app bundles and uses them to make QuickLook capable of understanding more document formats.

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.

jwells89··on The Vision Pro reportedly suspended because of weak demand
I still use mine for the things I watch by myself (with TV filling its usual role for social watches). I want to try it for other purposes but keep forgetting to.
jwells89··on Goldman and Apple 'illegally sidestepped' obligations to credit-card customers
It's also nice that the cash back is actually cash which can be automatically directed into the accompanying savings account, where it accrues 4.10% APY interest. None of the usual funny business with points with shifting valuations, restrictions on how they can be spent, etc.
jwells89··on "Somebody Tranq That Child!"
I may be misinterpreting, but I think that what the quoted post is talking about is probably independent from the kind of development you’ve mentioned.

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.

jwells89··on Skeptical of rewriting JavaScript tools in "faster" languages
A bit of extra verbosity as added by static typing can also be immensely helpful for trawling through and/or learning an unfamiliar codebase, especially in the absence of an IDE or debugging environment (e.g. browsing code on GitHub or in a filemanager).

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.

jwells89··on Apple's macOS Sequoia lets you snap windows into position
That preference is totally legitimate. There are however many types of power users, including those who extensively customize and augment their desktops and sync their dotfiles, as well as those who know all the key shortcuts, tips and tricks, etc but run mostly-stock configs.

I’m in the latter camp and it’s exceptionally rare that major OS updates break anything for me.

jwells89··on Apple's macOS Sequoia lets you snap windows into position
macOS has plenty of power user affordances, they're just Apple/NeXT-flavored rather than Windows/Linux-flavored and might not be as immediately obvious to users coming from other platforms.
jwells89··on Apple's macOS Sequoia lets you snap windows into position
As noted in another comment thread, there's a setting to disable margins when tiling so that's probably not an issue. IIRC Microsoft and Apple have a patent-sharing agreement (which is why MS Surface products have MagSafe-cousin power plugs).

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.

jwells89··on Apple's macOS Sequoia lets you snap windows into position
Music on macOS is really weird architecturally. Parts are native, parts are WebViews, and I wouldn't be surprised if there's even still some bits of code leftover from the days Music/iTunes was still known as SoundJam MP.

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.

jwells89··on Apple's macOS Sequoia lets you snap windows into position
Another vote for Moom here. By default it doesn't have any Aero Snap style drag zones and only presents itself as a hover-popover attached to the green button, which is perfect for my use of snapping which is only occasional. Its ability to divide your screen into a grid of your choosing is nice too.

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.

jwells89··on Running an open source app: Usage, costs and community donations
Spinning up a VPS for things like this is tempting to me too, but not having done significant backend work in over a decade my worry would be with administering it — namely keeping it up to date, secure, and configured correctly (initial setup is easy). What's the popular way of handling that these days?
jwells89··on Reinventing Core Data Development with SwiftData Principles
That's a great point and I agree, but it'd be nice if it weren't necessary to pop the hood to debug garden variety issues. The simplicity of UIKit in that regard is hard to beat.
jwells89··on Reinventing Core Data Development with SwiftData Principles
Unfortunately debugging challenges aren't unique to SwiftUI. Having having your application code get buried underneath miles of framework magic in stack traces can also be experienced with Jetpack Compose.
jwells89··on MacOS sometimes leaks traffic after system updates
In my experience, when filetype associations change under macOS it’s because some app I’ve used recently has made those changes without asking me.

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.

jwells89··on MacOS sometimes leaks traffic after system updates
I’m very confident that it’s either this or the restore-after-crash feature that OP is seeing. I don’t think it’s anything specific to Safari, because I have never seen Safari opened before login when it’s not my default browser.

That said, there should probably be a checkbox in system settings to disable login “prewarming”.

jwells89··on The state of GNU/Linux and a case against shared object libraries
The other big downside is a dependency tree that is better described as a rainforest with all of the third party widgets that you'll likely be importing, each of which comes with is own set of quirks, shortcomings, level of QA and maintenance, preferred development style, etc.
jwells89··on The state of GNU/Linux and a case against shared object libraries
At the moment, no not really. Some of the other options improve on Qt’s weaknesses, but only at the cost of its strengths (for example, if you want a tableview/datagrid with sortable, rearrangable columns like is standard in Qt Widgets and AppKit, more “modern” options Flutter and Jetpack Compose aren’t options because they lack such a widget).

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.

jwells89··on The state of GNU/Linux and a case against shared object libraries
With a disclaimer that I'm not an expert on Qt:

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

jwells89··on The state of GNU/Linux and a case against shared object libraries
In my opinion, what desktop Linux needs to attract the the sort of developers that create the high-polish third party software that macOS is known is a combination DE and UI toolkit that provides the same breadth and depth that's found in AppKit.

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.

jwells89··on HHKB and Realforce – Mechanical Programming and Gaming Keyboards
HHKBs themselves are great but for me the main point of attraction is the layout. It takes a bit to get used to, but it works very well for me. Especially on macOS with its system wide text nav key shortcuts, it allows just about everything larger boards do while requiring significantly less hand movement. No home/end cluster or numpad either pushing the alpha cluster way off center or pushing the right-hand mousing area way out is nice too.

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.

jwells89··on Software Engineer Pay Heatmap Across the US
Niche might make a difference too, with demand and supply levels varying between them. Don’t know what the current market is like but in the past my experience has been that niches with higher barriers to entry see significantly fewer applicants (and thus, less competition per position).
jwells89··on The best browser bookmarking system is files
Perhaps. In my case bookmarks tend to be append-only because going through and reviewing them for relevance, link rot, etc is tedious, which then makes finding bookmarks later more difficult, particularly when it’s been long enough to not remember the title/address of the bookmark. Tags can help but like folders lose effectiveness with number of bookmarks.
jwells89··on The best browser bookmarking system is files
I appreciate how universal and decoupled this approach is, but it doesn’t fix my main problem with browser bookmarks which is that management overhead gets to be problematic and makes me want to not bookmark things unless there’s adequate “justification” for doing so.

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.

← PreviousPage 2 of 34Next →