I have recently looked at utilising Swift to update an old Carbon based application. I stopped pursuing this path Swiftly, in part because of lack of good support for sockets and generally problematic use of CG* code.
I tried a completely new approach - Electron. I have found Electron to be surprisingly quick to prototype, easy to bridge to c++, and is cross platform (non mobile at least). I would not have recommended a non-native approach until recently, but for what it is worth, I've come to realise this is one of the better options available these days. YMMV. Sam On Tue, 1 Oct 2019, 06:09 Jens Alfke via Cocoa-dev, < cocoa-dev@lists.apple.com> wrote: > > > > On Sep 30, 2019, at 8:16 AM, Robert Walsh via Cocoa-dev < > cocoa-dev@lists.apple.com> wrote: > > > > however, to use it to do anything other than building a desktop or IOS > GUI application seems to result in code with messy syntax and what seem to > me to be hacks in order to bridge between NS* and CG* code. (Lots of casts > and strange machinations for massaging pointers.) > > This is true when calling C code from any language that isn't based on C > :) Bridging between different languages is not a simple thing (I've done a > lot of it…) Take a look at how you call C code from Rust, Go, Java,Python, > etc.; it's at least as complex. > > > Also, as you've said Swift makes cross-platform development nearly > impossible because, even though Swift itself is available on other > platforms, the pre-built components that prevent the developer from having > to reinvent every wheel from scratch are not. > > This is true, but getting less so. There's pretty good support for > server-side Swift now, apparently. > > Both of these are complaints about the immaturity of the Swift libraries, > not about the language itself, and the good thing is that libraries are > much easier/faster to build than languages. > > —Jens > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/thesquib%40gmail.com > > This email sent to thesq...@gmail.com > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
