3 ms·
I spent 20 years writing in object oriented C, the last three in objective C. When Swift was announced I started my next project in it, and never switched back.
by valuearb 8y ago
I spent 20 years writing in object oriented C, the last three in objective C. When Swift was announced I started my next project in it, and never switched back. That’s saying a lot giving how rough Swift 1.0 was, I couldn’t even release till Swift 1.2.
The entire language is designed to make the most costly part of development, quality, so much easier. That’s been it’s main purpose and theme since day one. And it’s not just optionals.
Today some code wouldn’t compile because I forgot a switch case. I remembered when I didn’t have to worry about stuff like that, Objective C would let me compile and defer till weeks later finding the obscure bug it caused in a painful multihour debugging session.
- mpweiher 8y ago> 20 years writing in object oriented C C++?
- valuearb 8y agoThink/Lightspeed C for much of it, using their object Oriented extensions.
- mpweiher 8y agoSo essentially C++? "Version 3 and subsequent versions were essentially a subset of C++ and supported basic object oriented programming concepts such as single inheritance as well as extensions to the C standard that conformed more closely to the requirements of Mac OS programming. After version 6, the OOP facilities were expanded to a full C++ implementation, and the product was rebranded Symantec C++ for versions 7 and 8, now under development by different authors" https://en.wikipedia.org/wiki/THINK_C https://en.wikipedia.org/wiki/THINK_C
- valuearb 8y agoNah, never developed using C++, always stuck to the original object oriented subset.