3 ms·
I remember trying and finally getting the i86 version of NeXTSTEP 3.3 running. Ended up with a Digital 486 base with parts from about three other machines for s
by karmakaze 9y ago
I remember trying and finally getting the i86 version of NeXTSTEP 3.3 running. Ended up with a Digital 486 base with parts from about three other machines for supported SCSI adapter, video card, CD-ROM, and special startup incantations. When it finally booted in glorious 2bit (4-level grayscale and I'm not even being facetious), it was honestly all worth the effort.
Interface Builder was mind-blowing. It's why we have .nib (or is it .xib now) files on macOS as well as all the NS* classes. The layout constraint solver was really slick back then too.
I suspect that 'porting' the operating system, but not really supporting machines of the day didn't help.
- wpietri 9y agoYeah, I loved Interface Builder. In a sense, it's responsible for me mainly focusing on back-end work. Because after building GUI apps with IB and ObjC, writing anything for Windows seemed like stone knives and bearskins. I think the reason for modest hardware support was that at the time they were chasing the high-end custom development market that had been so receptive to their workstations. At the time I was working for financial traders. We were buying machines specifically to run our in-house software, so we were happy buying whatever was supported. Their strategy for broader adoption was OpenStep, which was taking the great NeXT-specific stuff and making it run on Windows NT. It would have been interesting to see where that went, but as you know Apple's acquisition put an end to all that.
- jonhendry18 9y ago"I think the reason for modest hardware support" Also they only had 250 or so employees. So not a lot of staff to track down hardware compatibility issues, and not a lot of motivation from vendors to help. That said, they did pretty well.