6 ms·
I was born in the late 1980s and thus was too young to experience NeXT in its heyday, but sometime in high school was when I learned Mac OS X and its NeXT herit
by linguae 6y ago
I was born in the late 1980s and thus was too young to experience NeXT in its heyday, but sometime in high school was when I learned Mac OS X and its NeXT heritage. I was enamored by a highly usable Unix GUI, and since then I've been a fan of Mac OS X and NeXTSTEP. I even own a non-working NeXTstation Turbo Color that I bought on eBay with the intention of restoring it.
However, I was so intrigued with NeXTSTEP as Unix with a polished GUI that I didn't realize or appreciate its Smalltalk influences until roughly a year or so ago. In a way, NeXTSTEP could be thought of as the realization of a polished Smalltalk desktop, albeit with Objective-C and Unix rather than actual Smalltalk. On one hand, NeXT lacks Smalltalk's image-based, live-object environment, which I think is something that would still be revolutionary if a desktop operating system environment offered this today. (My dream is a desktop based on live objects, but the substrate I'd personally pick would be the Common Lisp Object System with its support for multiple dispatch.) On the other hand, Objective-C brought the benefits of Smalltalk-style message-passing object-oriented programming to NeXTSTEP programmers while being compatible with C, which was important for supporting an ever-growing base of software written in C. NeXTSTEP also sweetened GUI programming through its Interface Builder, which was originally for Lisp.
On a somewhat related note, there were attempts by Apple to catch up to NeXT or to even leapfrog them. The Pink/Taligent project would have created a modern operating system (e.g., one with preemptive multitasking and memory protection) with an object-oriented API, though that API was in C++ instead of something more dynamic such as Smalltalk, CLOS, or Dylan (Apple's own internal language that was heavily Lisp-influenced but had an Algol-like syntax). Unfortunately this project failed, which led to a scaled-down effort called Copland (the original plans for Mac OS 8) which also failed, which ultimately led to the purchase of NeXT and the return of Steve Jobs.
- codpiece 6y agoCome join us over at http://www.nextcomputers.org/forums/ http://www.nextcomputers.org/forums/ you can find the part you need to fix that machine. There's also a NeXT emulator, Previous that works really well.
- pjmlp 6y agoIn case you still haven't seen this, https://www.nextop.de/NeXTstep_3.3_Developer_Documentation/ https://www.nextop.de/NeXTstep_3.3_Developer_Documentation/ http://www.kevra.org/TheBestOfNext/BooksArticlesWhitePapers/NeXTStepDevelopersLibrary/NeXTStepDevelopersLibrary.html http://www.kevra.org/TheBestOfNext/BooksArticlesWhitePapers/... "NeXT vs Sun" commercial, https://www.youtube.com/watch?v=UGhfB-NICzg https://www.youtube.com/watch?v=UGhfB-NICzg https://opendylan.org/ https://opendylan.org/ https://www.macintoshrepository.org/531-mac-os-8-0-copland-beta-builds- https://www.macintoshrepository.org/531-mac-os-8-0-copland-b... https://tech-insider.org/mac/copland.html https://tech-insider.org/mac/copland.html
- scroot 6y agoHere is a question I can't quite answer: why is the complexity of something like Xcode so much greater than NeXT, when many of the basic UI components are pretty much the same kinds of things they were 20 years ago (but, subjectively, better looking)? Is all this extra complexity warranted?
- lorenb 6y agoNope
- bergstromm466 6y agoWhat makes (parts of) Xcode essentially bloatware or have warrantless extra complexity, to a certain extent, in your view?
- andrekandre 6y agoi can only speak from memory, but when xcode merged interface builder into the ide (before it was xcode + interface builder) eveyrthing became so slow it was almost intolerable i wonder if glomming two apps together must have caused some aweful redundancies that slowed up everything?
- bergstromm466 6y agoAwesome thanks, if you can think of anything later, please add!
- kazinator 6y ago> I was so intrigued with NeXTSTEP as Unix with a polished GUI Don't forget, also, about NextSTEP being based on the Mach kernel plus code from BSD Unix.