[HN Gopher] Catching Native Apps
       ___________________________________________________________________
        
       Catching Native Apps
        
       Author : bangonkeyboard
       Score  : 40 points
       Date   : 2022-01-12 22:27 UTC (1 days ago)
        
 (HTM) web link (mjtsai.com)
 (TXT) w3m dump (mjtsai.com)
        
       | egypturnash wrote:
       | god what is going on with this page, Safari keeps on deciding to
       | stop rendering anything when I scroll up, none of the links work
       | when I hover over them, it breaks Reader mode too.
       | 
       | edit: oh now that I bitched about it here it's loading fine, how
       | peculiar.
        
       | PaulDavisThe1st wrote:
       | The more fundamental question here is: why, given what we know of
       | the market share of devices running macOS, would anyone choose to
       | develop solely for macOS (and thus target Apple-provided APIs)?
       | 
       | Now, let's be clear. I am not insisting that there are no reasons
       | why anyone would do this. If you believe (rightly or wrongly)
       | that your audience/user niche is overwhelmingly macOS-based,
       | that's one pretty good reason right there.
       | 
       | But ... yep, truth be told, I can't imagine any other good
       | reasons. If you're developing native applications in 2022,
       | targetting a single platform makes almost no sense unless you
       | pre-define your audience as limited to that platform. You may be
       | able to create a viable revenue model doing that, but for every
       | user on your chosen platform, there's somewhere between 2 and 20
       | who are irritated by your decision.
        
       | valleyer wrote:
       | > three competing app frameworks won't create it
       | 
       | > Apple splitting their resources to support AppKit, SwiftUI, and
       | Catalyst probably doesn't help.
       | 
       | Yup. After years trying to coalesce development around AppKit
       | (transitioning away from the original Toolbox API), Apple decided
       | to ship the org chart and simultaneously maintain three different
       | UI frameworks, none of them fully consistent with the others.
       | Engineering labor was divided between them, and extra work was
       | created due to interoperability requirements. All three were left
       | worse off as a result.
        
         | [deleted]
        
       ___________________________________________________________________
       (page generated 2022-01-13 23:00 UTC)