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 Testing the Firefox Alternatives
Yep. While Sidebery, TST, etc have done about as well as they can given the limitations of extensions, the resulting vertical tab experience is half-baked without userChrome mods. It's also still kinda janky even with the mods unless one spends time polishing out all the edge cases, but then there's a high chance the mods will randomly break in weird ways after an update one day. There's real value in having the feature be native.
jwells89··on Exploring the scalable matrix extension of the Apple M4 processor
Overall, GPU strength is the best it's ever been in portable Apple devices by a significant margin. The problem isn't the hardware, it's that game developers are reticent to support anything that's not x86 Windows+DirectX or one of the consoles.

It's often said that macOS/iOS supporting Vulkan would help and while I think that's true to an extent, native Vulkan support is still rare enough that it's not going to change all that much in terms of ease of porting. It might improve things on the front of running games through WINE (DirectX → Vulkan translation), but unless developers produce ARM builds of their games there's always going to be the overhead of being run through an x86 translator, which varies depending on how CPU heavy the game is.

jwells89··on A Stock Prius just drove across America averaging 93.158 MPG
Really depends on how batteries develop, in my opinion. If we see a jump in energy density and charging speeds that allows e.g. a VW Golf sized car to have a range of 400-500 miles (with larger vehicles with larger batteries being able to go even further), the appeal of hybrids diminishes significantly. That’s a good enough range to close remaining gaps in the NA charger grid and longer than many ICE cars can go without a refill.
jwells89··on SpaceX update regarding Starship FAA flight approval
> Every US launch site is next to a de facto or a de jure wildlife refuge.

Yes, this is difficult to avoid for various reasons, perhaps the most pertinent being that all the safest places to launch things from are along coastlines where it's easy to divert wayward rockets into the ocean and away from populated areas. Coastlines have plenty of water and thus plenty of wildlife. Launching from e.g. an inland desert is much more risky and the environmental impact isn't necessarily all that much better to boot.

jwells89··on Why VR Games Still Haven't Taken Off
As someone who's spent a large amount of time in Beat Saber I think half the problem is that as good as VR headsets have gotten since the introduction of the original Rift, they're still full of compromises. None of them do everything well, and so you have to pick the one that sucks the least for a single use case (fitness games, racing/flight sims, VRChat, etc), and that's really bad for something as expensive as VR headsets are (even the cheaper quests).

In the case of Quest stuff, PC link users being treated somewhat as second class (no direct DisplayPort input) and the lock-in of the crappy Quest desktop software doesn't help matters.

I agree that VR will always be a niche, but I would also say that there's a good chance of the niche growing with the introduction of a well-built, affordable, well rounded headset that's built on the SteamVR ecosystem.

jwells89··on Sony announces PS5 Pro, a $700 graphics workhorse available Nov. 7
For games that old the most trouble-free option is probably a Windows 2000 or XP VM using some VM software that offers graphics acceleration.
jwells89··on Sony announces PS5 Pro, a $700 graphics workhorse available Nov. 7
Particularly if you want to play with a controller (as is common for a living room/couch setup). Windows somehow has the worst controller support out of all operating systems (including mobile OSes) and if it weren't for Valve patching things up with Steam, it'd be almost unserviceable in that category.
jwells89··on iPhone 16 Pro and iPhone 16 Pro Max
App bloat really is out of control, to the point that I wonder if maybe Apple shouldn't somehow incentivize developers to minimize bundle size and resource consumption. Maybe well-crafted, efficient apps get an "eco friendly" badge and their own section of the App Store or something.
jwells89··on iPhone 16 Pro and iPhone 16 Pro Max
I've noticed overall improvements in responsiveness as well as the number of apps that can stay in memory without some getting evicted, though the latter is most noticeable when using smaller indie sorts of apps (think Ivory for Mastodon, Narwhal for Reddit, etc) which are on average built more efficiently and aren't dragging around a metric ton of tracking garbage.
jwells89··on Understanding the Layout Process in Qt Widgets
I've seen a few blogposts on the subject over the years but wouldn't be able to reference any of them on short notice.

In short though, frameworks like SwiftUI tend to be designed around a very narrow set of use cases and if yours deviates from those in any way you're in for a bad time, and depending on how great the deviation is will likely land you with falling back to older imperative frameworks for their more customizable/hackable widgets in places (if that's an option) or dropping the declarative framework altogether.

jwells89··on Understanding the Layout Process in Qt Widgets
> I can't speak for the author, but many systems programmers look at declarative/markup-based UI as a kind of black magic that you can't trust and that will get in your way sooner or later by not leaving a sane way for you to address some project requirement.

This exact scenario has played out for many trying to adopt SwiftUI. For even moderately complex projects it’s common to get 90% of the way there fairly easily, only for that last 10% to be a struggle/slog as a result of its inflexibility. AppKit/UIKit may not be trendy or sexy and might take longer to get new projects spun up with, but it’s much more rare to hit that brick wall with them; you’ll probably be able to accomplish what you need with little or no pain.

I’ve seen shades of this in Jetpack Compose too, which makes me think that these sorts of problems are just inherent to the type of UI framework.

jwells89··on Boox Palma Review: A Phone-Sized E-Ink Android Device That Isn't a Phone
I use the Pocket functionality pretty frequently, it's nice for tossing articles and other things I'd like to read over to the Kobo from whatever I happen to be using at the moment.
jwells89··on Is my vision that bad? No, it's just a bug in Apple's Calculator
QA for iOS has slipped in recent years, but I feel that’s a different matter. The issues I have with Android aren’t bugs, it’s more like odd choices for things like animation timing curves and nitty gritty things like that.

Bugs aside, it feels like touches more “directly” control iOS whereas with Android it’s like interactions are all passing through an additional layer, leading to an impression of disconnectedness. It’s not entirely unlike the phenomenon that used to be observable on some Linux desktops a decade+ ago when computers were weaker and you could “feel” the layering of X11, GTK, your compositor, DE, etc all kind of slip-sliding and not acting fully in concert, where Windows and OS X usually didn’t give this impression.

jwells89··on Is my vision that bad? No, it's just a bug in Apple's Calculator
Ideally, you want a screen that natively runs at a resolution that’s a perfect 2x multiplier of a mainstream 1x resolution that has the right amount of screen real estate for the screen size.

So for example, a 20”-24” screen should be 4K so it can run at 1920x1080 @ 2x. Similarly for 27”, you want 5K which is 2560x1440 @ 2x.

This is a really good post describing how it all works:

https://bjango.com/articles/macexternaldisplays2/

jwells89··on Is my vision that bad? No, it's just a bug in Apple's Calculator
Even when expanding scope to include laptops that run Linux well despite not officially supporting it, the selection available still have major issues, whether they be with build quality, screen panel quality, battery life, standby time, sleep/wake, overall lack of fit and finish (e.g. unthoughtfully placed ports) or some combination thereof.

It seems like a near impossibility for other manufacturers to not phone some of those things in. There’s always a catch.

jwells89··on Is my vision that bad? No, it's just a bug in Apple's Calculator
The thing that keeps me on iOS is that Android just doesn’t feel right, and none of the tweaks that can be applied (launchers, etc) can fix that. Animations, interactions, etc just feel… off somehow, like I’m using an early alpha build of software that has placeholders strewn about.

It’s not a “it’s not iOS” thing, either. There are certain desktop Linux setups for example that don’t bother me nearly as much. It’s just Android that feels “wrong”.

If only the entire front end of Android were interchangeable like Linux DEs are.

jwells89··on Is my vision that bad? No, it's just a bug in Apple's Calculator
It’s kinda tough, because a clean-cut, coherent vision of how the OS is intended to be used is necessary to build a great experience. The more you try to accommodate ways of usage beyond that, the more the vision falls apart and you end up with checkbox waterfalls and branching tunnels of config dialogs added in the pursuit of making everybody happy.

So realistically, judiciousness is required to keep it all glued together, and some usage patterns just won’t be accommodated.

For example, Apple doesn’t seem to be bending over backwards to make former Windows users happy, because the way that desktop works is just too different from what they’ve envisioned and what their long time users are used to. If they add a series of toggles to support Windows usage patterns, that’s a sudden 2x multiplier on the behaviors and UI that needs to be tested.

That said, I don’t necessarily agree with all of Apple’s decisions (I’ve never liked the linear representation of virtual desktops that in place since 10.7 Lion that well and preferred 10.6’s Snow Leopard’s 2D grid, for example), but the lines have to be drawn somewhere.

jwells89··on Is my vision that bad? No, it's just a bug in Apple's Calculator
I’m not sure that they’re an unknown concept, because macOS has lots of little things tucked away all over the place for power users. It’s one of the things I miss most when using other desktops, particularly those that go maybe a little too far on the minimalism thing (like GNOME).

It’s just that they expect these users to have fairly specific usage patterns and design around those. The further one’s personal patterns deviate from that expectation, the higher the level of friction encountered.

jwells89··on Our slowly growing Unix monoculture
I think there’s probably small but strong market for “Linux MacBooks”, as in laptops with the same or better level of fit and finish and attention put towards things like battery life, standby time, reliable sleep/wake, etc and are designed with Linux in mind.

All the current options, even those geared towards Linux specifically, make significant tradeoffs in one or more of these areas, and I think this significantly curbs Linux adoption.

jwells89··on Memos: stick private notes on your email
I think you're right in that the trend started with Outlook, but at least for a while Microsoft offered an opt-out in the form of Outlook Express, which was just a mail client.

My preference is that email and calendar are two entirely separate apps, because I have my calendar open for about half of the emails I compose, and the remainder of my calendar usage has nothing to do with email at all. This is one of the reasons I've stuck with Apple Mail + Calendar through the years.

jwells89··on Window Maker: X11 window manager with the look and feel of the NeXTSTEP UI
I agree that using FreeBSD as the base OS probably isn't necessary, but it does make sense if they're trying to provide an alternative to macOS, with the macOS userland much more closely resembling FreeBSD's than GNU's. There are BSD-styled Linux distros that could serve this purpose too, though.

The problem with using almost any existing DE as a base is that Linux DEs are all inclined toward non-mac UI paradigms (most being Windows-like and a couple iPad-like), which means required changes will be numerous and deep. So much so that the benefit of not starting from scratch is dubious.

jwells89··on Window Maker: X11 window manager with the look and feel of the NeXTSTEP UI
> If I were them I’d just port one of the many macOS looking desktop environments like whatever ElementsryOS or PopOS uses to FreeBSD and build from there. That’s obviously more productive, but productivity can be boring because it’s real and not a hobby project. :P

I’m not sure how much productive it’d be in the long run, at least if faithfully replicating macOS is the goal. PopOS is bailing on GNOME (what it had been using) in favor of a bespoke DE because modifying GNOME had become too much of a pain, even for their relatively modest changes. Pantheon (elementary’s DE) closely resembles GNOME for likely similar reasons.

Not that any of the other DEs would serve as better bases, unfortunately. No matter what making a Mac-style DE is going to be a steep uphill climb.

jwells89··on COSMIC Alpha Released
Totally true that it's not possible to catch all edge cases, but I don't think it's a strong enough reason to rule out user theming/customization altogether, plus as mentioned parameterization should be done anyway for good accessibility.
jwells89··on COSMIC Alpha Released
To me, this is a big argument as to why devs should be making heavy use of parameterized values their UIs, as opposed to hardcoding things. An app making as much use of parameterized values as possible will not only remain decent looking and usable under most themes (except for themes that are badly built — nothing can help there), but also play much more nicely with accessibility settings like font size, font weight, colorblindness modes, etc.

I will caveat this by saying I haven’t worked with GTK and don’t know how well-tooled it is in this regard. If GTK doesn’t offer any/many parameterized values, then that’s on GTK, not app devs. They’re pretty well supported in macOS/AppKit, iOS/UIKit, and Android/Compose though and should be a cornerstone of any modern UI framework.

jwells89··on COSMIC Alpha Released
Not the OP, but while my X1 Nano runs Linux beautifully, its CPU and battery life are disappointing and it’s a bit on the slow side when unplugged, because getting what little battery life it’s capable of requires putting it in throttled down low power mode. It also spins up its fan for almost nothing.

I love the form factor, feel, weight, screen, etc… it’s really just the CPU that is ill-fit for the machine. I wish I could swap it out for a low-voltage Ryzen or Snapdragon, which would probably add 4-6 hours of life on the same battery.

This also doesn’t seem to be fixed on the newer Nano’s, which last I knew for some incomprehensible reason make use of higher power Intel Core models instead of the low voltage U-class CPUs that suit it better.

jwells89··on COSMIC Alpha Released
On top of no special casing for the terminal, I find the meta key (as positioned on Mac keyboards, to the left/right of space) easier to reach than the standard Control position. That’s also addressed by replacing Caps Lock with Control, though (which I build my keyboards and remap laptops to).
jwells89··on COSMIC Alpha Released
Having packages land in that goldilocks zone of not cutting edge but not old either is particularly pertinent for multiplatform users. It can get annoying trying to keep everything pinned on macs and windows boxes to match distros that are slower to update.

I could totally see using something like Debian stable in a pure Linux environment with no newly-supported hardware being added, though.

jwells89··on Clay (short for C Layout) is a high performance 2D UI layout library
There's a fair deal of resources for writing code-only UIs in iOS apps with UIKit, but not nearly as much for Mac AppKit apps.

I suspect that this is because the average Mac window/view nib file is a great deal less complex than its counterpart view nib on iOS and still manageable to edit in Interface Builder, and so a lot of Mac devs still use nibs.

I've toyed with code-only Mac AppKit stuff but generally have found that it's not quite as clean as code only iOS UIKit. For example if I recall correctly, there's no initializer for NSWindow that sets all of the flags that make it behave like a normal window because it's assumed that you'll be using nibs. It's not difficult to write an extension to NSWindow to fix this, but it has to be done for reasonable productivity, and these papercuts are strewn throughout AppKit. In contrast, most UIKit controls can be initialized with few or no arguments and still behave as expected.

jwells89··on Clay (short for C Layout) is a high performance 2D UI layout library
When IB really went downhill is when it got merged into Xcode, in my opinion. Performance and stability took a big hit and it never fully recovered.
jwells89··on Eazel, ex-Apple led Linux startup
Elementary's aesthetics are in the right place, but Pantheon is probably too closely coupled with GNOME to allow the degree of freedom such a group would desire. Depending on GTK, which has become well known for pulling rugs from underneath devs using it, is also a liability.

Considering these things I believe such a group would be best served by starting their own DE project and likely writing their own UI framework with first-class C bindings, because while Qt doesn't break things as often as GTK does it's restrictive in the languages it can be used with.

← PreviousPage 4 of 34Next →