9 ms·
The origins of Objective-C at PPI/Stepstone and its evolution at NeXT
- ChrisMarshallNY 6y agoWow. “Software-ICs.” I remember that, and I thought it was a great concept. At the time, it was revolutionary. Nowadays, it’s how we do everything, but the term “Software-ICs” never climbed out of the bassinet.
- twoodfin 6y agoThe problem wasn’t nomenclature or technology, it was economics: Part of the premise of “Software-ICs” was that, like physical ICs, a market would develop in software components that could rival the existing “shrink-wrapped” software industry in size. That never came close to happening, for reasons that it would be fun to speculate about. Perhaps one could make the case that it’s finally happening except as “cloud services ICs”.
- protomyth 6y agoWell, the old VBX market was pretty robust. I remember receiving catalogs in the mail advertising components to add to a Visual Basic project.
- badsectoracula 6y agoSame for Delphi, MFC and to a lesser extent WinForms. I think the rise of open source libraries simply killed that market and with the web being steeped into open source mindset from the get go, it never took off there.
- protomyth 6y agoI'm not sure it was the mindset or just no real mechanism for making isolated components.
- badsectoracula 6y agoThere isn't much of a mechanism in any of those, the components were essentially libraries. Sure, in Delphi and VB you get a tiny icon to represent the component and a visual property editor, but that doesn't really translate web stuff that is 100% text-based. AFAIK MFC has nothing visual.
- protomyth 6y agoWindows had a whole mechanism with VBX and OCX for building the components and keeping their innards isolated. Javascript had no equivalent.
- badsectoracula 6y agoYes, but this was only for Visual Basic. Delphi, MFC and WinForms each have their own and is just a library. JavaScript also had libraries since, if nothing else, you can always load multiple scripts per html page. Also, FWIW, i wasn't only referring to JavaScript but also server-side too (e.g. PHP or Python or whatever).
- pjmlp 6y agoThe market is still there, the customers I work for, keep buying such components, even in 2020.
- linguae 6y agoI wonder what would have happened to the Linux desktop ecosystem had it embraced something like Software-ICs modeled similarly to Apple's OpenDoc project rather than to implement monolithic applications. One of my favorite Hacker News comments describing what could have been is this (https://news.ycombinator.com/item?id=13573373 https://news.ycombinator.com/item?id=13573373). My views are in line with this comment; I believe that component-based software is a more efficient development model, and I also believe that this would provide necessary differentiation of the Linux desktop ecosystem compared to commercial desktops like Windows and macOS. I'm actually planning a side project where I want to implement a component-based application framework on top of Linux and the BSDs, but using the Common Lisp Object System as its base as part of a long-term vision to build a modern-day Lisp operating system (I want to focus on the application environment first, leveraging the wide hardware support that Linux and the BSDs have compared to lesser-known operating systems like Mezzano). I haven't heard of the term Software IC until now, but I'm familiar with the history of the OpenDoc project as well as other component-based software technologies such as SOM, COM, CORBA, and XPCOM.
- twoodfin 6y agoThe fundamental problem is that no matter how much more efficient a component-driven model is for developers, users don’t want it. To a first approximation, nobody wants to assemble their own software, or even choose amongst assemblies made by a zoo of “integrators” who turn components into applications. Developers want this, and indeed they benefit from a developer-focused OS like Unix that builds on the component model. But that’s the outer limit of the market for components.
- sontek 6y agoI think that happened for awhile in the early 2000s. I know we purchased a lot of UI component libraries back in the day. But I think we all had a enough of those component development companies go out of business or deprecate the version we were using that we are gun shy on doing it again. I know I stick with opensource only at this point for that very reason. At least if they decide to stop supporting me, I can support myself.
- mpweiher 6y agoYes, and I still think it still is great concept. :-) I also don't think it's really how we do everything, the original concept caught on only very partially, and appears to be more and more forgotten. See Software-ICs, Binary Compatibility, and Objective-Swift https://blog.metaobject.com/2019/03/software-ics-binary-compatibility-and.html https://blog.metaobject.com/2019/03/software-ics-binary-comp...
- twoodfin 6y agoThat’s a great post. Building “component-oriented” software platforms is a fascinating mix of CS theory and gritty practical engineering. I’m disappointed to hear even Swift couldn’t produce a satisfying result under their constraints & trade-offs.
- pjmlp 6y agoVery nice article. Regarding COM's approach, I just wish that Windows team would care to take more inspiration from Delphi, C++ Builder and .NET integration of COM (now UWP) into their infrastructure instead of coming up with "macho programming" frameworks like ATL/WRL. C++/CX seemed to actually hit a sweet point, almost like C++ Builder's approach, but it was overthrown due to the championing of C++/WiRT, not much better than WRL in regards to productivity. I still hope that if C++/WinRT gets as much push back as UWP happened to suffer, maybe Windows DevTeam will finally accept that providing nice tooling is something that C++ developers on Windows also enjoy having access to.
- mwcampbell 6y agoWhy do you say C++/WinRT is not much better than WRL in productivity? I strongly disagree. I work on the Windows accessibility team at Microsoft. We use C++/WinRT in new code that both consumes and implements WinRT components. So far, I'm happy with it and would not want to go back to C++/CX. C++/WinRT is definitely more productive than WRL.
- pjmlp 6y agoIt might be more productive than WRL, but it certainly isn't more productive than C++/CX and keeping with that mentality is what will keep us to actually embrace it, unless we are getting paid to do so. Here is the bullet points I keep giving back when asked for feedback. - No Visual Studio support for syntax highlighting or completion of IDL files - The fact that IDL files have to be manually edited to start with (C++/CX does it in the background). - The fact that those manually edited files have to be copied back into Visual Studio projects, after cppwinrt generates new files out of them. Again, something that isn't required with C++/CX - The fact that for data binding some types like bool, we need to go fully in and make use of x:Bind, thus, again manually having a new view model class, instead of directly binding via DataContext. Again, C++/CX has no issues with it. - XAML designer integration is still lacking versus the C++/CX experience, which manually editing IDL files doesn't make it more enjoyable - The amount of type juggling between hstrings, std::string, com_ptr, box, winrt::make, agile_ref and all the stuff that isn't required when using C++/CX - Constantly being told that we must just suck it up, and hopefully ISO C++23 or who knows when, will provide the necessary features regarding reflection and metaclasses, to add back to C++/WinRT the tooling experience that we already have today with C++/CX and is being dropped on the floor with the push of C++/WinRT - The fact that C++/WinRT keeps being pushed forward, yet like 90% of MSDN still provides examples and documentation using C++/CX, or that some problems migrating from C++/CX into C++/WinRT are only to be found in StackOverflow answers or comments discussing cppwinrt issues. Going back to WRL example, it is hardly any better than ATL was. C++/CX was the closest that Microsoft ever was with proving a C++ RAD like experience similar to C++ Builder. Apparently that isn't the path that Windows team wants to travel, there is .NET for that, and being better than WRL is already considered mission accomplished. Even MFC provides a better way of doing GUIs than what WinUI with C++/WinRT is giving us, but yeah I it is better than WRL I guess.
- dwheeler 6y agoNo, Brad Cox thought that the only way reuse could happen at scale would be via micropayments, which of the time he considered to be integral to the software IC idea: https://deprogrammaticaipsum.com/brad-cox/ https://deprogrammaticaipsum.com/brad-cox/ It turns out, of course, that the assumption was faults, and trying to track every dynamic use of software to pay its makers was completely impractical. What actually happened is similar to what happened with tcp/ip. The phone companies couldn't see how it would be useful, because its lack of per packet accounting meant it couldn't charge for every packet. Instead, by throwing away all the complex accounting systems, TCP/IP could grow far behind what the phone system could do.
- microtherion 6y agoMy impression is that micropayments were a later evolution of his thinking. When I met Cox in the mid-90s, his talk focused on micropayments as a newer concept. Stepstone started out by selling bundles of "Software ICs", after all, for a price that was rather "macropayments".
- comex 6y agoIn some sense the idea was just ahead of its time. After all, micropayments are a reality today with the hosted APIs and high-level cloud services that seem to be all the rage these days – services where the primary value-add is in the software that someone’s running for you. It’s not exactly the same concept, but pretty close. Not that I’m a fan of the trend.
- protomyth 6y agoFor more of Brad Cox's thinking see his book "Superdistribution: Objects as Property on the Electronic Frontier".
- microtherion 6y agoVery interesting paper. I was a bit puzzled, though, at the assertion related to the Stepstone graphics libraries that X11 was still "years away". The chronology of the paper is not 100% certain in that area, but my impression was that this assertion was set in something like 1987/88, and X11 was released in late 1987.
- pjmlp 6y agoI guess it has more to do with the bare bones X capabilities and the alternatives like NeWS.
- gdubs 6y agoThis is a wonderful bit of history, really grateful to have it. I remember reading an interview with Steve Jobs in Wired magazine in the 90s where he talked about the future being all about Objects – "The Next Insanely Great Thing" [1]. I built my career on top of Objective-C. These days I really enjoy Swift, but I still have a space in my heart for the dynamic beauty of Objective-C. 1: https://www.wired.com/1996/02/jobs-2/ https://www.wired.com/1996/02/jobs-2/
- jrochkind1 6y agoRuby is probably one of the current languages most like ObjC in it's bones, at least in certain dimensions, due to them both being so influenced by smalltalk. But ruby isn't necessarily doing great as far as market share either. :(
- gdubs 6y agoIt's been a while since I've used it, but before I made native apps I had a little web development business going, and used Ruby on Rails extensively. I couldn't articulate the similarities at the time with ObjC, but looking back I'm sure it had a lot to do with my comfort working in Ruby. And, I credit that web work I did in Ruby with my becoming a better programmer. Being able to drop in to low-level C for real-time applications (audio, in my case) was a great aspect of ObjC. Though there were plenty of times I wished I could program in ObjC in the real-time threads. There were many debates on the Core Audio forums about whether ObjC was safe in real-time threads. Most of Core Audio was developed by C++ programmers, and their default was to avoid ObjC out of a fear that a surprise lock or memory allocation would glitch out the audio. There was, however, at least one NeXT veteran on the forums who felt this was nonsense, and recalled writing device drivers in ObjC.
- mpweiher 6y ago> one NeXT veteran on the forums who felt this was nonsense, and recalled writing device drivers in ObjC So did I. https://www.nextop.de/NeXTstep_3.3_Developer_Documentation/OperatingSystem/Part3_DriverKit/Concepts/1_Overview/Overview.htmld/ https://www.nextop.de/NeXTstep_3.3_Developer_Documentation/O... It was quite lovely, and I later heard from Apple kernel devs that moving to C++ from Objective-C was one of their biggest regrets.
- miohtama 6y agoEventually software industry revolution was brought by an open source movement and likes of NPM and PyPi repositories.
- anthk 6y agoCPAN existed several years before.
- MintelIE 6y agoObjective-C was a very interesting language, in some ways much better than C++ while filling the same type of role. It's a shame that so much effort is being thrown away by Apple. I recommend anybody who has an Objective-C program that they don't wish to rewrite in Swift to look into GNUstep. I personally have two Objective-C projects which I will not be porting to Swift, instead I will port them from Cocoa to GNUstep.
- justinmeiners 6y agoIf it is non-GUI I also recommend Objfw
- frou_dh 6y agoWhere's the pressure to rewrite an existing application in Swift coming from?
- wool_gather 6y agoI'm curious why you feel the need to port them at all? ObjC is pretty far from dead. Perhaps the ObjC runtime will be abandoned by Apple at some point, but I can't see even deprecation (not removal from their shipping systems) taking less than a decade. In particular, note that Swift on Darwin platforms is intimately tied to the ObjC runtime. I wouldn't be surprised if there are long-range aspirations to change that, but it's not feasible in any short term.
- NelsonMinar 6y agoIn 1994 I was on a team that had one of the few uses of Objective C that had nothing to do with NeXTStep. The Swarm Simulation System[1], an agent based simulation toolkit. We used GNU's Objective C implementation and Tcl/Tk (via tclobjc) for the UI. We picked ObjC because we knew we wanted something object oriented but C++ seemed too complicated and too static. ObjC was simple and appealingly dynamic and flexible in its type system. It worked pretty well for us other than the costs of being an oddball language no one knew. But it was simple enough to learn that a fair number of our target audience did. In retrospect I wish we had the courage to use Smalltalk or a Lisp system but at the time that felt too risky. Java was also just beginning to be an option then, but it was still being shown as a toy for making applets and not a real programming language. Also very slow before JITs. I really appreciated that the ObjC runtime was open source and very small. It was quite easy to get in deep and understand what was going on. [1] http://www.swarm.org http://www.swarm.org
- jmuhlich 6y agoI have fond memories of using Swarm in an undergrad course on agent based simulation ~20 years ago. Just tweaking the heatbugs example in various ways was already enlightening. Thanks for your work!
- lukeh 6y agoBack in 1996 I ported a fairly large (exactly how big I forget) workflow framework that had been developed in Objective-C on NEXTSTEP to Windows. It didn’t use Foundation, so we didn’t need much beyond gcc and some general portability elbow grease.
- pjmlp 6y agoAnd in 1999 I ported a particle simulation engine from Objective-C/NeXTSTEP into Windows/C++, because the university departments were getting rid of their Cubes and my supervisor wanted to rescue some of the department work. The turns that the world does.
- matchbok 6y agoGlad it's going away, the syntax is a chore to read and understand. There's no valid reason for the use of brackets.
- saagarjha 6y ago100% compatibility with C isn’t free.
- gmac 6y agoThere’s also no valid reason for the non-use of brackets, is there? They’re just different. It didn’t take long for them to feel natural to me when I started coding in ObjC, and the named method parameters that go with them make ObjC code (in my eyes) delightfully self-documenting.
- andrekandre 6y ago> different. It didn’t take long for them to feel natural to me when I started coding in ObjC definitely, and for people like me, who started coding when they were young (on mac/ios) there was no bias for or against such syntax (i also learned c++, and java at the same time and have no special love or hate for those syntaxes either) i think alot of these "i hate this syntax" issues are people just not liking what they were not used to...
- apple4ever 6y agoI hated the brackets at first but after using ObjC for a bit I came to love them.
- beska 6y agoIt’s amazing how many peopled are triggered by square brackets.
- herodotus 6y agoGood article, so glad to find it here. I wish, though, that the authors had talked a lot more about memory management in Objective-C, because this had a major impact, not only on the development of Objective-C, but also on Swift. As far as I can tell, the idea of (explicit) reference counting came from Next, when Blaine Garst and others were working on remote objects. When I joined Apple (and therefore had to learn Objective-C), the most important task was to understand reference counting and memory management. Yes, there was a lot more, like interfaces, properties and the many libraries, but understanding alloc/new/release/autorelease was crucial for shippable software. GC was introduced (and deprecated) during my time, but it was the realization (presumably by Lattner and his team) that the LLVM analyzer could do a better job than humans at managing reference counting that was huge. No more hours and hours hunting down memory leaks! And, of course, only one concept required in Swift, namely weak vs. strong references. In summary, a terrific paper, but it is too bad that this crucial part of the story is missing.
- gdubs 6y agoIndeed; reference counting was one of the most important aspects of Objective-C. Probably the most difficult aspect of it was that while most of the time method names have hints as to what increased a reference count, it wasn’t always obvious. And then, of course, you had Core Foundation functions which could be tricky to grok in terms of memory.
- asveikau 6y ago> As far as I can tell, the idea of (explicit) reference counting came from Next, Maybe in objc, but in the general case I kinda doubt this. It's a very common pattern in kernel development as an example, haven't done any archeology here but I have seen it in codebases rooted in the 80s at latest, probably earlier. (Did original Unix reference count file objects in the FD table the same way a modern kernel would? Would not be surprised if yes.) Autorelease is pretty unique though and clever.
- herodotus 6y agoGood point. I really meant reference counting as implemented in the Objective-C runtime architecture.
- watersb 6y agoSoftware ICs (Integrated Circuits)