> Le 30 sept. 2019 à 17:16, Robert Walsh via Cocoa-dev > <cocoa-dev@lists.apple.com> a écrit : > > > Swift may be the solution, but it's built on a weak foundation. It makes > cross-platform development almost impossible. The TIOBE index shows Swift > declining (and Objective-C increasing). So, maybe it isn't. > > I don't yet have a lot of experience with Swift, but I would already argue > that Swift is not the solution. Swift is cool and has some really neat > features that make for good presentations and blog posts (where the > real-world issues and constraints associated with interfacing to other > systems, particularly older ones that do not use HTTP, can be minimized or > eliminated entirely); 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.) I'm in the > process of converting an application written in C++ using an older version of > Qt because the Qt code relies on Carbon (which has been removed from > Catalina). The new code is in Swift. I've written and maintained code that > uses UNIX-style C sockets for many years, but finding a native approach for > plain sockets in Swift was very > difficult. There appears to be good support for async HTTP communication, > but not much for socket-based TCP.
SwiftNIO is protocol agnostic, and let you manipulate any data stream as you like. Moreover, it is cross platform (unlike the lower level Network Framework, which is far superior to using unix socket IMHO, but can’t be use for cross platform dev). _______________________________________________ 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
