6 ms·
I bought a C compiler at my job in 1984 because I thought it was the future, then spent nearly a decade writing MacOS apps in C. I even added object extensions
by coldcode 4y ago
I bought a C compiler at my job in 1984 because I thought it was the future, then spent nearly a decade writing MacOS apps in C. I even added object extensions to it (for our use) in 1989 because C++ was not an option yet.
I worked with Objective-C in the late 90s and again in the 2010s, which is basically C with funky object stuff.
I don't miss it at all. C is very low level and so easy to write bad code in if you don't have solid discipline, the language doesn't help at all, which was not really a design decision back then. The first C compiler we used didn't even support prototypes.
I exclusively use Swift now.
- Koshkin 4y agoOnly a mother could love Swift's syntax. The classic K&R C, on the other hand, was the very definition of simplicity and elegance. (Objective-C is a whole another topic, of course.)
- KerrAvon 4y agoClassic K&R C? Where you declared the function arguments Pascal style out of line and had to rely on separate “lint” programs to check for typesafety in function calls? Surely you mean C89, where functions have some type safety but C’s variable declaration syntax remains a horrible inelegant kludge? Have you written much code in Swift?
- pyth0 4y agoI really don't understand this take at all. Swift has fairly standard syntax as far as modern languages go.
- pjmlp 4y agoWhat about MPW, MacApp and Metrowerks PowerPlant?