3 ms·

> It is not clear at the moment if Apple has any plans to port Swift UI to Windows and/or Linux It seems pretty clear they have 0 plans on doing that. They cou

by myko 6y ago

> It is not clear at the moment if Apple has any plans to port Swift UI to Windows and/or Linux It seems pretty clear they have 0 plans on doing that. They could've open sourced it in the first place, along with Combine. Not open sourcing Combine seems like a pretty short sighted decision to me.

thought_alarm 6y ago
The important aspect of SwiftUI is tight integration with AppKit and UIKit. SwiftUI for Win32 (or whatever) would be a completely different beast. There's nothing stoping anyone from implementing such a thing, just as someone wrote a SwiftUI for HTML. All the pieces are there, but it would be a huge amount of work unrelated to SwiftUI on Mac and iOS.
ken 6y ago
Swift wasn't originally open-source, either.
- plorkyeran 6y ago
  They announced that it would be open-source in the future almost immediately.
  - comex 6y ago
    Not "almost immediately". They announced it would be open source at WWDC 2015, a year after Swift was first introduced at WWDC 2014. The actual open source release then happened a few months later in December 2015.
- scarface74 6y ago
  Not only did they announce that it would be open source immediately, unlike the source code dump they did with WebKit, Apple made the entire git commit history public from the initial commit.
  - bdash 6y ago
    FWIW, WebKit's complete history is available in its Subversion repository, all the way back to the initial commits in 2001 when they were importing KHTML and convincing it to compile without Qt. Granted, there was around two years after Safari's initial release where Apple simply published source code drops, but the full code history has been public (first in CVS, then in SVN) since mid-2005.
  - ken 6y ago
    Where? Here's the transcript of the initial announcement [1]. No mention of open source that I see. Dr. Dobb's had an article in 2014 [2] which said "Swift is proprietary and closed: It is entirely controlled by Apple and there is no open source implementation." EDIT: I found a HN post from 2015, just over a year after Swift was released, titled "Swift will be open source later this year" [3]. Not immediate at all. [1]: https://asciiwwdc.com/2014/sessions/101 https://asciiwwdc.com/2014/sessions/101 [2]: http://www.drdobbs.com/architecture-and-design/swift-objectively/240168424 http://www.drdobbs.com/architecture-and-design/swift-objecti... [3]: https://news.ycombinator.com/item?id=9680982 https://news.ycombinator.com/item?id=9680982
ynx 6y ago
hard to open source it when its implementation is tied to the XNU kernel
- noodlesUK 6y ago
  XNU is one of the few parts of macOS that is actually open source. I’d be pretty surprised though if swiftUI were deeply dependent on the kernel itself, rather than on some graphics toolkit within macOS
  - saagarjha 6y ago
    It’s largely dependent (but not reliant) on the UI libraries.
jmull 6y ago
It seems like it could still be coming. They might be following the same pattern for SwiftUI (and Combine) that they used with Swift itself: 1. Create and introduce it as proprietary 2. Iterate fast, changing a lot of things to improve it quickly. 3. Stablize 4. Open source it (and continue iterating with an open process) The advantage to starting proprietary is the initial iteration phase can move move quickly and stay focused on the goals of the people in the controlling group.

by myko 6y ago

thought_alarm 6y ago

The important aspect of SwiftUI is tight integration with AppKit and UIKit. SwiftUI for Win32 (or whatever) would be a completely different beast. There's nothing stoping anyone from implementing such a thing, just as someone wrote a SwiftUI for HTML. All the pieces are there, but it would be a huge amount of work unrelated to SwiftUI on Mac and iOS.

ken 6y ago

Swift wasn't originally open-source, either.

plorkyeran 6y ago
They announced that it would be open-source in the future almost immediately.
- comex 6y ago
  Not "almost immediately". They announced it would be open source at WWDC 2015, a year after Swift was first introduced at WWDC 2014. The actual open source release then happened a few months later in December 2015.
scarface74 6y ago
Not only did they announce that it would be open source immediately, unlike the source code dump they did with WebKit, Apple made the entire git commit history public from the initial commit.
- bdash 6y ago
  FWIW, WebKit's complete history is available in its Subversion repository, all the way back to the initial commits in 2001 when they were importing KHTML and convincing it to compile without Qt. Granted, there was around two years after Safari's initial release where Apple simply published source code drops, but the full code history has been public (first in CVS, then in SVN) since mid-2005.
- ken 6y ago
  Where? Here's the transcript of the initial announcement [1]. No mention of open source that I see. Dr. Dobb's had an article in 2014 [2] which said "Swift is proprietary and closed: It is entirely controlled by Apple and there is no open source implementation." EDIT: I found a HN post from 2015, just over a year after Swift was released, titled "Swift will be open source later this year" [3]. Not immediate at all. [1]: https://asciiwwdc.com/2014/sessions/101 https://asciiwwdc.com/2014/sessions/101 [2]: http://www.drdobbs.com/architecture-and-design/swift-objectively/240168424 http://www.drdobbs.com/architecture-and-design/swift-objecti... [3]: https://news.ycombinator.com/item?id=9680982 https://news.ycombinator.com/item?id=9680982

ynx 6y ago

hard to open source it when its implementation is tied to the XNU kernel

noodlesUK 6y ago
XNU is one of the few parts of macOS that is actually open source. I’d be pretty surprised though if swiftUI were deeply dependent on the kernel itself, rather than on some graphics toolkit within macOS
- saagarjha 6y ago
  It’s largely dependent (but not reliant) on the UI libraries.

jmull 6y ago

It seems like it could still be coming. They might be following the same pattern for SwiftUI (and Combine) that they used with Swift itself: 1. Create and introduce it as proprietary 2. Iterate fast, changing a lot of things to improve it quickly. 3. Stablize 4. Open source it (and continue iterating with an open process) The advantage to starting proprietary is the initial iteration phase can move move quickly and stay focused on the goals of the people in the controlling group.