The nature of software is to always be evolving. COBOL jokes aside, it’s rare to find programming frameworks that reach a level of maturity and support that allow them to just exist without being supplanted by a newer language or a better abstraction. Which naturally is great. Who wants to find themselves writing software with the expectations of today while performing the tasks of manual memory management or manipulating strings that are just raw pointers in a block of memory terminating with a null (\0) character? But sometimes in this constantly evolving space, you find a framework that resonates, and you hold on to it tightly. I wanted to share how this happened for me, first with Ruby (no surprise) but then oddly with Objective-C.

source: L

With the birth of Swift, we face the passing of Objective-C. To mark this historic moment, long-time Objective-C developer and trainer Aaron Hillegass delivers an impassioned eulogy for a language he knew well.

This is a nice recap of the development and early days.

source: HN

This error is caused by changes in how fork() behaves in High Sierra.

Another problem that could have been avoided if people read the manual.

Some more info: http://www.sealiesoftware.com/blog/archive/2017/6/5/Objective-C_and_fork_in_macOS_1013.html

source: HN

It’s always interesting to dive into framework internals. objc_msgSend in particular is a work of art, and delightful to read through.

Some notes on objc interop.

Another objective C compiler and runtime, based on just C.