4 ms·
This is an other step in the direction to a Swift-only Apple platforms. I don't think it would be worth my time to even buy a other macOS device to port my fra
by stephc_int13 4y ago
This is an other step in the direction to a Swift-only Apple platforms.
I don't think it would be worth my time to even buy a other macOS device to port my framework.
I don't think they will get any benefit from this.
- musicale 4y agoIt's a good question as to how long Apple will support calling its APIs from C++ via Objective-C++. I don't see any good reason for them to deprecate the ObjC-Swift bridge, but I guess they could decide it's too much work to maintain.
- stephc_int13 4y agoObjective-C was/is an awful programming language, one of the worst I ever had the displeasure to work with. But at least they relied on the LLVM toolchain and the NeXTStep heritage, it was possible to use clang and many C APIs and a few wrappers around the horrible Obj-C APIs. With Swift I don't think this will be as practical, if even possible. They are so rich and powerful that they don't care. And most devs on their platforms are happy to drink the kool-aid. This will take time, because they have relatively strong foundations and deep pockets, but they are going to slowly sink their ship, what they are building these days is technically unsound and pretty soon their engineering culture will have completely changed.
- lukeh 4y agoWhen the last ObjC framework is gone? Surely that’s decades away. There are zillions of frameworks in PrivateFrameworks, many written in ObjC. The Swift/C++ bridging stuff is pretty exciting though. A lot of engineering is being thrown into this.