asdasd
About
- Username
- asdasd
- Joined
- Visits
- 248
- Last Active
- Roles
- member
- Points
- 1,785
- Badges
- 1
- Posts
- 5,686
Reactions
-
Apple reportedly evaluating Apple Silicon-powered macOS on iPhone
The Mac OS UI is clearly not suitable for the small screen of the iPhone. Your fingers are too big. The text is too small. It just doesn't work. This has nothing to do with technical limitations or anything like that. Or ideology. It won't work, so they won't do it.. Apple is clearly diversifying their OS lines, not the opposite. -
Apple reportedly evaluating Apple Silicon-powered macOS on iPhone
Also how does the transition happen. You are running 5 apps on your iOS device and writing some notes. Then you come home, plug it into the monitor and the iPhone now mirrors onto the monitor except it is now showing the apps as Mac OS apps, rather than iOS apps, which means they are bigger and multi-documented and dont use touch interfaces. So you work on that for a while and save a few windows and put some files on the desktop and then take the iPhone away but the iPhone doesn't have access to the desktop, the multiple windows are gone, and everything is different in layout.
The iPad with a keyboard is slightly more believable, it is closer to the Mac, but not totally. I mean if you were to imagine a few years back a merger between iOS and Mac OS, then the modern iPad OS is it. But it is still not Mac OS.
In the future if iPads can power monitors, why would you plug an iPad into a monitor and get Mac OS? Maybe a version of iPad OS will work with monitors in the future, maybe a menubar will appear when you plug it in. Maybe you have some access to the desktop when you plug it in. ( I doubt it). If apple does that they will call still it iPad OS. -
Apple reportedly evaluating Apple Silicon-powered macOS on iPhone
No, this is not going to happen. When Jobs introduced the iPhone he said they put OS X on it. In effect that was what it was. A modified version of OS X.
Then they decided to create a new OS, called iPhone OS, now iOS, to differentiate. Then they broke iOS into iPad OS. Then they created watchOS. Then they created TvOS. Carplay. All are based on the same original OS.
Whats happening here? Are they differentiating? Yes, they are. Why then would they throw it all back together again?
You can in fact use similar, or mostly the exact same code ( with Swift UI in particular) to create apps for all of these Oses.
But thats not the point of differentiating the OS, the point is the user experience. A Mac has huge screen real estate, an iPad less, an iPhone even less. A watch, the least. And therefore they also need different UX and UI. The point and click of the mouse vs the touch of the other devices. Or the wheel on the watch. A menubar vs none. A filesystem vs none.
If an app with the same code ( swiftUI or catalyst) is built for Mac OS and iOS they will look different on either OS, that's the point. And even then with complex apps you are almost certainly going to want to break out custom code for either platform. Mac OS isnt going to work at all on the smaller device. iOS isn't going to look good on the larger device. Hooking a phone to a monitor to get it to look like MacOS sounds terrifically stupid to me. This is kinda like how CarPlay works ( CarPlay can be a separate screen running from your device but on the dashboard). But that doesn't scale up at all to a PC/Mac and photoshop etc. aren't going to scale down to the iPhone either, not without looking totally different. ( I doubt if their OS X apps and iOS apps are exactly the same code, catalyst and swiftUI are not that powerful and too new).
So a big rewrite for the big app devs to have cross platform apps in the same binary.
And what's in it for Apple. A device that can attach to a monitor so people dont have to buy a Mac? And for the user? An underpowered "Mac" which is a dumb monitor with bad cross platform apps which kills your device's battery.
-
Apple unveils plans to ditch Intel chips in Macs for 'Apple Silicon'
Peza said:asdasd said:Peza said:mjtomlin said:Peza said:If the road this ends up going down means the same apps on a Mac are the same apps on an iPad, then surely Apples PC market share is going to shrink even further, everyone will just buy a much cheaper iPad.I’m not questioning Apples silicone prowess here, I’m questioning if developers will follow them down the path.
Ummm, there’s over a hundred million Mac users. Developers will follow - it’s not a “hire a new team and rewrite all your code” obstacle. It’s a click-a-button and recompile inconvenience for 99% of developers.
Marketshare is not a metric you use to decide if you’re going to take time and develop software for a particular platform - what’s more important is user base and which versions of the OS is being used the most.
https://www.google.co.uk/amp/s/appleinsider.com/articles/19/10/10/mac-shipments-grow-slightly-but-apple-pc-market-share-shrinks/amp/
I have to say that I don’t think that market share equates to hundreds of millions of Mac users.
I’ve already read comments from music professional stating a lot of their old legacy plugins etc will no longer work. And the developers are either not in business anymore or too small to worry about Apple and spending money if an Apple silicone dev kit.“Rosetta can translate most Intel-based apps, including apps that contain just-in-time (JIT) compilers. However, Rosetta doesn't translate the following executables:
- Kernel extensions
- Virtual Machine apps that virtualize x86_64 computer platforms”To me that doesn’t sound like something that can be fixed with ‘a single click’.
And reading the posts in the forums there, it would mean a VM machine will have to ‘emulate’ my Windows and it’s apps to work not Virtualise them, I don’t enough about it to know if that’s true but it makes sense, virtualising X86 programmes on X86 platforms. And emulation doesn’t tend to work as well or perform as well.
in any case you mistook two things, what works in rosetta and what can be done in Xcode.
Here is a fairly quick explanation of what has to be done, and for most apps its just a recompile and if you use other libraries, getting them to recompile first. Plugins take a small amount of extra work.
https://developer.apple.com/videos/play/wwdc2020/10214/
Remember that Microsoft and Adobe have already done this, it took years in the OS9 - OS10 transition to get this done.
-
Apple unveils plans to ditch Intel chips in Macs for 'Apple Silicon'
Peza said:mjtomlin said:Peza said:If the road this ends up going down means the same apps on a Mac are the same apps on an iPad, then surely Apples PC market share is going to shrink even further, everyone will just buy a much cheaper iPad.I’m not questioning Apples silicone prowess here, I’m questioning if developers will follow them down the path.
Ummm, there’s over a hundred million Mac users. Developers will follow - it’s not a “hire a new team and rewrite all your code” obstacle. It’s a click-a-button and recompile inconvenience for 99% of developers.
Marketshare is not a metric you use to decide if you’re going to take time and develop software for a particular platform - what’s more important is user base and which versions of the OS is being used the most.
https://www.google.co.uk/amp/s/appleinsider.com/articles/19/10/10/mac-shipments-grow-slightly-but-apple-pc-market-share-shrinks/amp/
I have to say that I don’t think that market share equates to hundreds of millions of Mac users.
I’ve already read comments from music professional stating a lot of their old legacy plugins etc will no longer work. And the developers are either not in business anymore or too small to worry about Apple and spending money if an Apple silicone dev kit.