6 ms·
As a former NeRD (NeXT Registered Developer) who started a company that did custom NeXT development, I both strongly agree and strongly disagree. The technolog
by wpietri 6y ago
As a former NeRD (NeXT Registered Developer) who started a company that did custom NeXT development, I both strongly agree and strongly disagree.
The technology really was great. Their understanding of object orientation was superior. The developer tools were wonderful. The user experience was generally a delight. We could develop custom software in a fraction of the time of people using the tools of the day. NeXT had a true vision of the future.
However, what they didn't have was much understanding of economics. The only reason that NeXT wasn't a complete commercial failure was that Apple's board wanted Steve Jobs back. If not, Apple might instead have bought out Be. And if Apple had succeeded in developing their own next-gen OS, both NeXT and Be might be minor footnotes these days. Even prior to the deus ex machina buyout, NeXT was on a slow and steady path to failure. They'd gone from an integrated hardware vendor to an OS-on-other-hardware vendor to a dev-tools-on-other-OSes vendor, and it's not clear that would have worked either. Once the acquisition was announced, they promised to take care of the people who had stuck with them and then did jack.
I took a few lessons away from my time with NeXT. 1) Just because I thought something was technically superior didn't mean it was commercially viable. 2) Being too far ahead of the market is worse than being behind it. 3) Never trust a "visionary leader" to look out for you, no matter what he says. He's in it for himself and the vision; the little people are expendable.
But you're definitely right that it made using other stuff painful. I stopped doing GUI development altogether rather than shift to Windows, which was incomparably awful by comparison.
- markus_zhang 6y agoThanks for sharing. Can you elaborate a bit why GUI development for NeXT was (and probably is) superior comparing to Windows GUI development (even if we include Borland's effort).
- alblue 6y agoAt the time of NeXT’s heyday in the early ‘90s, most GUI programming was textual. You’d call add(button) and button.text = “Hello World” to build up your GUI, and have to wire up the events from your button to take specific actions. Quite a lot of GUI programming is still like this, even now. What NeXT brought was a GUI editor that allowed you to drag a button from a palette and onto a window (or view). You could then change the text on the button by double clicking on it and renaming the default text. You also got to determine where and how large the button was in relation to the rest of the window. Most GUI builders could do this, so what was special about Interface Builder? Two things stood out. First, you could specify how the button reacted to window resizing. There was a “springs and struts” layout mechanism that allowed you to say which parts were fixed offsets and which were variable. You could also say if the button would resize, and if so, in the X or Y or both directions. The second thing was the ability to connect the button to an action. By Ctrl clicking and dragging, you could wire up the default action to a “selector” — in effect, a virtual method call, on the owner of the button. This owner would be populated at startup, typically the application (controller). So you could have your code with the responder and another team build the UI, and they would join together at runtime. You could also use properties generated by code as well - you could connect the button’s field to an object’s property (aka an outlet) so that changing the code changed the UI. The fact that you could drag and drop connections from UI to code, and from code to UI, as well as building a responsive UI, was really what stood out. This still lives on in Xcode today; IB and PB begat Xcode and IB which begat Xcode. The “nib” format - Next Interface Builder - was a binary format file containing the descriptive state of the Ui and the wiring requirements, which was renamed “xib” when XML became all the rage is the same thing. The fact that IB has been subsumed into Xcode still hides the fact that is what’s happening under the covers. I think it’s important to realise that this was in an age when Windows 3.1 was all the rage, and we had only just got out of 256 colour VGA while Next station had 16 million. Nowadays with everyone doing MVC programming with the web, it doesn’t seem so important. But then there was a time when no one wrote unit tests because it was seen as pointless; but it is from these seeds that ideas become mainstream.
- altcognito 6y agoI’m sure that your aware that Ms access, Delphi, Visual Basic, progress as well as a host of other tools existed at the time, and you’re fine to point out that Next was superior but given that really none of these systems survived, something else must be going on.
- stjohnswarts 6y agoWhat? Delphi and the Microsoft tools are still available. They did survive they just didn't prosper I suppose you could say.
- alblue 6y agoSure, but Delphi was released in 1995 as the first version, whereas this was something I was programming in 1992 (and I came late to the party with Nextstep 3). https://en.wikipedia.org/wiki/History_of_Delphi_(software) https://en.wikipedia.org/wiki/History_of_Delphi_(software) Visual Basic came out in 1991, by which time Nextstep was already at version 2.1 So yes, these things existed, but after Next had demonstrated them.
- altcognito 6y agoThe timeline was off in my head, it was a long ago!
- oumua_don17 6y agoAnd original Interface builder was developed in Lisp :) [1] [1] https://paulhammant.com/2013/03/28/interface-builders-alternative-lisp-timeline/ https://paulhammant.com/2013/03/28/interface-builders-altern...
- markus_zhang 6y agoThanks. This looks slick and ahead of its time. GUI development has also been a bit messy or heavy and I wish we had easier solutions nowadays.
- 6y ago
- jrochkind1 6y agoI don't think you are disagreeing with anything I said, let alone strongly -- I didn't say anything about economics! Thanks for sharing though! I suppose it may be that technical excellence has never been economically viable, and NeXT survived as long as it did only by fluke.
- Godel_unicode 6y ago> technical excellence has never been economically viable I think Google search would like to have a word with you.
- mywittyname 6y agoGoogle could have -- and probably would have -- failed if not for Google Ads. The great search results drove people to use their product, but it didn't actually earn them money directly. You can have the best product on the market and fail, and you can have a terrible one, yet succeed. Google has as much business acumen as they do technical chops, and that's why they are such a success. Same with MS and Apple.
- Godel_unicode 6y agoI'm lost, you're saying because their product has a monetization strategy that it doesn't count somehow? By that logic, we've reduced the statement I'm replying to into the tautology "cool products with no monetization strategy aren't monetized". Doesn't have quite the same ring to it. Edit: I guess if we want to limit it to cool technologies that are directly monetizable, the ford motor company of the early 20th century (or maybe Tesla) is a better example? It's just as silly a statement either way.
- mywittyname 6y agoI'm just saying that technical excellence is orthogonal to how much money a product makes. There is a ton of shit software out there that makes buckets of money, and lots of well designed, well executed products never make it off the ground. So you can't just focus on good engineering and expect clients to line up out there door.
- chungus_khan 6y agoNeXT was also mostly ahead of the market on the software side. Their machines were a very tough sell compared to the price and performance of other UNIX workstations of the time (which is why I know SunOS and not NeXTStep). All the vision and all the software quality in the world won't make you competitive in the 90s UNIX workstation market if your machines are underpowered, and we were used to garbage software anyway. Chasing the "personal workstation"/PC market also would never work. DOS/Windows was far too strong and the Macintosh deep in a niche. It's very unfortunate.
- kjs3 6y agoNeXT failed on the hardware cost side because they wanted to be a personal computer and not a workstation. They were priced for neither market. I looked very seriously at Unix machines around the time NeXT came out, having been converted to that religion in college. NeXT started at around US$6500, and that was with the optical disk only. The equivalent-ish Sun box (Sun 3/80) started at around US$15k with disk as I recall and went up in price really fast if you wanted more memory/disk/etc. About the cost of a new Honda Accord at the time. And the Sparcstations were out at much higher performance (and price...I seem to recall around US$22k for a usable config). On the other hand, you could get a nicely decked out 386/33 for maybe half the cost of the NeXT, or a 486 for a grand or so more. And it ran tons of software, even if it was garbage. Even Unix.
- myrandomcomment 6y agoThis is a good comment. To put more data here: 1st NeXT Computer 1988: Motorola 68030/25Mhz w/68882 FPU, 64MB RAM max. MIPS: 4 Sun Workstation 1988 Sun-4 line: Spac @ 16-33Mhz, 32-768MB RAM MIPS: 7-114 Now having used both, the desktop and usability on the NeXT was so much better.
- GlenTheMachine 6y agoThe low-end NeXTstation was $2999 if I recall correctly. I had one. For the price you couldn’t get a faster machine.