Re: Which ObjC2.0 features are missing in the latest GCC?

[Riccardo Mottola]

Hi,


On 11/24/19 10:11 AM, Max Chan wrote:
> I would like to add another plus for dropping GCC: if we want any hope 
> for Swift interworking, we have to use clang as the compiler.
>
> Apple have no plan to provide any GUI support on Linux version of 
> Swift. If we have Swift interworking, even though we may have to drop 
> our own libobjc, Foundation and CoreFoundation in favor of Apple’s 
> release, the GNUStep GUI package can provide the replacement AppKit 
> that Apple’s Swift release lacked.

I would add that as a minus and warning point.

Should we really follow Apple blindly in these decisions? I don't think 
so. Apple's interest in MacOS long dwindled and became apparent in its 
renaming as macOS.

I personally don't care about Swift... but I would find if useful for 
the FOSS world if people could use Swift + GNUstep.


But here a question: what if in the future Apple will switch over to 
Swift totally? An evolution in the APIs and hypothetical Swift 2.0 which 
would make Objective-C incompatible. What then? Should GNUstep follow 
blindly?

It is the same question we are having here now, just time-shifted. I 
suppose you can guess my answer implicitly.


Riccardo