"To begin with, Objective-C 3.0 would have made header files entirely optional, and if you didn’t provide one, they’d be automatically generated from the implementation file. Just write your *.m files and save."
https://akos.ma/blog/what-objective-c-3.0-could-have-been/
=> More informations about this toot | More toots from akosma@mastodon.online
@akosma Haven't even clicked the link, much less read your article, and I like it already.
=> More informations about this toot | More toots from cocoadog@mastodon.social
@akosma Okay, now I've read it, and of course I really like it. 🙂
=> More informations about this toot | More toots from cocoadog@mastodon.social
@cocoadog 🤣😅🎉🙏
=> More informations about this toot | More toots from akosma@mastodon.online
@akosma
I still use Objective-C daily in my #NeoFinder, and even after all these years, I haven't found a good reason to throw it all away for much slower compile times and lots of interoperability problems, combined with almost no advantages at all...
🤗
=> More informations about this toot | More toots from cdfinder@techhub.social
@akosma one of the two things I miss the most about objective C are the header files particularly as they evolved in objc 2
=> More informations about this toot | More toots from dimsumthinking@mastodon.social
@akosma Cocoa Bindings didn’t make it to iOS, presumably because of performance problems. What if you could bind to a “firstName” and it didn’t matter if it’s via a method, function, or ivar (D has this). In the IB UI, it says “bound to ivar”, so you know it works at design-time and also compile-time. Go through all of AppKit and change the runtime duck typing to compile-time duck typing.
=> More informations about this toot | More toots from JonathanGerlach@mastodon.social
@akosma Somewhat related article of mine: https://www.alwaysrightinstitute.com/swifter-design/
=> More informations about this toot | More toots from helge@mastodon.social This content has been proxied by September (3851b).Proxy Information
text/gemini