News for hackers. Stuff that matters.
Re:SwiftUI and Catalyst: Apple executes its invisible transi... by pwinnski on Thursday June 13, 2019 @11:52AM (#20176044)
I think the difference is in the second step. Both companies excel in moving the target forward, but Microsoft rarely, if ever, shuts off access to the old targets, maintaining compatibility essentially forever, which keeps them from ever being able to make major transitions.

There are any number of ways to develop for Windows, and the fact that many, even most developers use Visual Studio is different from the Apple approach: everybody must use Xcode. This sucks for companies like MetroWerks that once developed a popular IDE for MacOS only to be shut out, but it's necessary to ensure that the tail end of the migration, that pesky step 2 of shutting things off, happens.

Re:SwiftUI and Catalyst: Apple executes its invisible transi... by brantonb on Thursday June 13, 2019 @01:01PM (#20176699)
I’m an iOS developer and I use AppCode as my primary IDE. It does have a dependency on Xcode, so it has to be installed.
Re:SwiftUI and Catalyst: Apple executes its invisible transi... by bluedino on Thursday June 13, 2019 @12:30PM (#20176419)
Microsoft never shuts off the old targets because otherwise nobody would ever upgrade to the next version of Windows