Earlier quoted context omitted.
As someone who literally abandoned Windows for the same reasons (during 8), macOS is still far far from sinking into those depths of depravity yet.
My worry though is that when Windows fucked up, Mac OS was a viable alternative. Now that Mac fucks up, what's the alternative? Linux has its own challenges.
Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
141–145 of 145 posts
Re: Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
#142Earlier quoted context omitted.
It shouldn’t be confounding. It seems clear: Apple views the Mac as an iPad with an attached keyboard and optionally cooling. There will be touch on the Mac very soon and they are preemptively getting the Apps ready. The whole Apple Silicon migration is to facilitate this merge of macOS and iPadOS. As soon as the 3 year migration to Apple Silicon is complete and most developers have stopped relying on Rosetta, Macs w…
What a depressing future we're headed into :/ Instead of iPad becoming a "proper" computer, the Mac is being dumbed down to become a tablet with a keyboard attached. Sometimes I wonder if the people making decisions at Apple, Google, Microsoft etc. live on a completely different planet than me.
The new iPad-Mac merge will have Xcode and maybe a Unix like terminal.
Re: Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
#143Earlier quoted context omitted.
I believe this changed as of Monterey.
Why would someone be forced into changing their entire operating system to get an update to an app? I just checked since I own multiple macs. It's true, they're going away from webviews, but their new native app ui is broken! When you go Browse, click the first big image and then press the back button in the top left corner, the white navigation bar space at the top disappears, causing the content below it to visibly…
...probably some APIs used that don't work on older OS's, and/or why bother supporting old Macs when the old app still works fine? I don't think it's a big deal.
Re: Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
#144It's really not an impressive showing for SwiftUI. 4 iterations later and after being told it's "the future" in unequivocal terms, it's still at 12% (and only like 3% without any AppKit combined (last chart)). It's not dogfooded for any productivity apps. For Ventura, rewriting "Font Book, System Settings, and Tips" is not exactly confidence inducing. If they rewrote Pages or Final Cut Pro, that would wake people up.…
>after being told it's "the future" in unequivocal terms Who told you this? :D SwiftUI is mostly useful for apps that show a bunch of nested lists. Basically websites, but natively. It's Apple's answer to React Native or something, and it looks cool in demos with the live preview and whatnot. But serious apps like Pages, FCP, Finder, Calendar, etc. will never be written with SwiftUI. The paradigm is just too wasteful…
Nonsense.
Re: Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
#145Earlier quoted context omitted.
> The majority of Mac users are producers That's not true at all, and sounds like Mac user elitism that everyone hates. It is true, that many iPhone users aren't interested in mac and some not interested in any kind of desktop/laptop device at all. The same true vice-versa - I have a mac* and not interested in iPhone and plenty of my colleges are the same. *: One because compliance is easier than on Linux and another…
Sorry, that's not what I meant, I incorrectly phrased that the wrong way around. If you are making stuff for iPhones, you essentially have to have a Mac because XCode to create iPhone apps requires a Mac to run. I meant the majory of app creators are Mac users. So if they kill the Mac workflow then they will castrate the cash cow that is the iPhone. I know there are alternative workflows you could make by using somet…
I would assume people at Apple aren't brain-dead to kill mac and not have an alternative development flow, haha. "killing mac" if it's on a table would include allowing other platforms to build iOS / iPadOS apps.