3 ms·
What's also interesting is that Objective-C and tools like InterfaceBuilder existed for 10+ years in near anonymity. NEXTSTEP was going nowhere, but fundamental
by ams6110 12y ago
What's also interesting is that Objective-C and tools like InterfaceBuilder existed for 10+ years in near anonymity. NEXTSTEP was going nowhere, but fundamentally it was MacOS X, and it existed in 1990. The language and tools and actually a lot of really cool applications were all there for years before Apple hit the right combination of platform and marketing that the market wanted. Just proves that a language's technical innovations don't mean much on its own.
- philwelch 12y agoIt did enable the hundreds-of-millions $ decision to buy NeXT for its system technologies.
- pjmlp 12y agoNot even close. NeXT was bought, because Steve Jobs was still there. I very seriously doubt Apple would care one second about NeXT if that wasn't the case.
- philwelch 12y agoSteve Jobs was an interesting bonus, but Amelio didn't plan to step down and let him take over. Jobs kind of forced his way in. The immediate reason Apple bought Next was for Nextstep. Apple had no next-generation OS and desperately needed one. The two viable options were Be and Next, and Next was considerably more mature.
- pjmlp 12y agoI remember very well the Copland fiasco, and the only reasons NeXT and Be came as options was that both owner companies were run by former Apple employees. The way enterprise does business, I doubt they would even be in the list if that wasn't the case.
- philwelch 12y agoBe that as it may, Steve Jobs' track record as of 1997 wasn't very promising. OK he founded Apple, but he alienated a lot of people along the way, was forcibly removed from upper management for being impossible to deal with, and was behind one massive flop in the Lisa and another admittedly brilliant product, the Mac, which fell short of expectations and had to be changed in ways Jobs would have never approved of to succeed (hard drives, cooling fans, expansion slots). After that, there was Next, which was a massive commercial flop in many incarnations until eventually becoming a vendor of an enterprise web application framework in the form of WebObjects. His biggest success was Pixar, where he essentially did little more than provide money and handle business stuff while John Lasseter ran the actual studio. Furthermore, the guy making the decisions was Gil Amelio, who probably wasn't looking to hire his successor as CEO. Amelio wasn't some interim appointment while they searched for someone to replace him, he was supposed to be the real CEO. Getting Steve Jobs back was a nice gesture for Apple fans and a nice story for the press but not the driving factor. The driving factor was that the Mac was dead without a new OS. Options other than Be and Next were considered, including Solaris and Windows NT, but Next was the preferred option and there were both business and technical reasons for that.
- nickik 12y agoWell befor the NEXT stuff took over Apple had things like Dylan in the pipeline. Dylan blows Objective-C out of the water, and it blows Swift out of the water. The tools devloped in Apple research where very advanced and very good, but the all got shutdown because of apples money problems. Then the change happend and we went to new system, most of the old research was never continued. Honsly while I was programming Objective-C I would often have visions of how the world could have been diffrent if Dylan, instead of Objective-C had become THE Apple language. I completly agree with you, most of the time, technical quality does not mean success.
- pmontra 12y agoOut of curiosity I googled for Dylan and this is what it looks like http://opendylan.org/ http://opendylan.org/ I think it's := a little bit => too heavy: with :: <punctuation>; but I like the use-of-hypens in symbols instead_of_underscores as in Lisp and as a common practice in CSS. So many shift keys saved! That should be the standard and who cares if we wouldn't be able to write a-b. a - b is more readable anyway. Check a large piece of code for a general feeling of the language https://github.com/dylan-lang/http/blob/master/common/http-common.dylan https://github.com/dylan-lang/http/blob/master/common/http-c... It's from 1992 so it's got a chance to influence Ruby (1995). If you look at both you'll clearly see many similarities in the general style of the language, despite Ruby making a lighter use of punctuation and that can have a large effect. Open that Dylan code side by side with this Ruby https://github.com/puma/puma/blob/master/lib/puma/server.rb https://github.com/puma/puma/blob/master/lib/puma/server.rb which has more or less the same role in a web server implementation. The main Dylan repositories have a fair amount of activity so it's a fringe language but not dead https://github.com/dylan-lang https://github.com/dylan-lang