3 ms·
I've had a similar experience, and generally agree with what you're saying. But I am glad Swift was created. All the plebs gravitate towards that language, so O
by jhatemyjob 3y ago
I've had a similar experience, and generally agree with what you're saying. But I am glad Swift was created. All the plebs gravitate towards that language, so Objective-C remains unpolluted. I shudder to think how Objective-C would have deteriorated without Steve around.
- wahnfrieden 3y agoObjC is often no longer an option for building on new platform functionality
- jhatemyjob 3y agoCan always use a shim
- MBCook 3y agoYeah but that’s a losing battle. As we go forward you’re going to have to shim out more and more of the new APIs that you need to use. Possibly in ways that are very inconvenient/hard to use in Obj-C.
- deleted 3y ago[deleted]
- jhatemyjob 3y agoIt's been 10 years and I haven't had any issues. Maybe in another 10 years this will be enough of a problem to switch, but by that point I'll be retired
- pjmlp 3y agoMetal is a counterexample of that.
- saagarjha 3y agoMetal is not a new framework
- pjmlp 3y agoMetal was released on the same year as Swift, could have been a way to show off Swift, instead used Objective-C with Swift bindings.
- saagarjha 3y agoThat’s because the Swift team almost certainly worked independently of the Metal team.
- pjmlp 3y agoHardly given that all Objective-C features since Objective-C 2.0 were aimed at improving the Swift interoperability story, as Chris Lattner has mentioned in a couple of interviews.
- saagarjha 3y agoHow is that related to what I said?
- pjmlp 3y agoThey were aware of Swift, and decided to make the upcoming OpenGL replacement framework in Objective-C instead of Swift, and only provide Swift bindings instead of doing it the other way around, implemented in Swift with Objective-C bindings for compatibility with "legacy" code.
- saagarjha 3y agoWho is "they"? Chris Lattner works on compilers under Developer Tools. The Swift and Objective-C teams share an office and are often the same people. Of course Objective-C is going to get new features to help import it into Swift, because the whole point of Swift was to make a new language that worked well with the old one. Basically nobody outside that group had any need to know of the language at that point, especially since it wasn't ready for system use anyways. I would not be surprised if the first time most of the Metal team even knew Swift existed was when Craig introduced it on stage at WWDC.