My misalignment with Apple's love affair with Swift

Re:My misalignment with Apple's love affair with Swift by archagon on Monday June 11, 2018 @08:42PM (#17289850)

For one, ObjC can't treat objects as values or initialize them on the stack. Also, the everything-is-an-object paradigm is terrible for arrays of values, since every NSNumber or NSValue has to be individually malloced and released. (Though maybe not the case anymore? It was certainly a chokepoint several years ago.)

Both of these factors have forced me into using lower-level Objective-C++ code on numerous occasions.

[ Parent | on HN ]

Re:My misalignment with Apple's love affair with Swift by mercutio2 on Tuesday June 12, 2018 @08:36PM (#17299315)

NSNumbers are generally tagged pointers, unless you’ve got a really large number.

[ Parent | on HN ]

Re:My misalignment with Apple's love affair with Swift by archagon on Tuesday June 12, 2018 @08:50PM (#17299370)

This didn't help me in my app, unfortunately, because I needed to encode CGPoints as NSValues. I suppose I could have resorted to ordinary, interleaved CGFloats, but it was way easier and more productive to just use C++ vectors. I knew exactly what I was getting with those, and I didn't have to do the boxing/unboxing dance.

[ Parent | on HN ]