[swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements

Adrian Kashivskyy adrian.kashivskyy at me.com
Fri Dec 4 07:39:28 CST 2015


> Removing Objective-C compatibility in Swift (which does not even have a complete set of libraries yet) in this stage would undermine its usability and the completeness of the libraries, and when the project finally matured a bad reputation of “incomplete support” would already be out there, hampering its use.

Could you point out five Objective-C Linux libraries (apart from GNU Foundation) that you'd like to use in your Swift projects on Linux? I suspect you can't and that's why I strongly disagree. You only need Objective-C on Apple platforms – and that's not going away. 

Maintaining Objective-C interoperability for non-Apple platforms is a very niche aim and could potentially lead to longer development and evolvement process. That's a reasonable tradeoff.

Pozdrawiam – Regards,
Adrian Kashivskyy

> Wiadomość napisana przez Maxthon Chan <xcvista at me.com> w dniu 04.12.2015, o godz. 11:54:
> 
> Let’s take a look at C# which Microsoft designed to replace C++ MFC. The compatibility is never removed although C# itself is pretty complete already. During early days (2002) lots of components in C# are stubs calling back to MFC but nevertheless this presented a more or less complete library set to the user and allowed the language to gain traction - so many traction that now people demand it to be ported to multiple platforms.
> 
> Removing Objective-C compatibility in Swift (which does not even have a complete set of libraries yet) in this stage would undermine its usability and the completeness of the libraries, and when the project finally matured a bad reputation of “incomplete support” would already be out there, hampering its use.
> 
>> On Dec 4, 2015, at 18:33, Alex Blewitt <alex.blewitt at gmail.com> wrote:
>> 
>> A more interesting question would be: is Swift designed to ultimately replace Objective-C? If so, baking in compatibility from the outset of the open source version would probably be going in the wrong direction.
>> 
>> Alex
>> 
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151204/59a39de6/attachment.html>


More information about the swift-evolution mailing list