5 ms·

From inside ParcPlace, it looked like we were starting to gain traction. There'd been a number of spectacular C++ project failures, and people seemed to be will

by dws 6y ago

From inside ParcPlace, it looked like we were starting to gain traction. There'd been a number of spectacular C++ project failures, and people seemed to be willing to try this weird, new (to them) thing that let them get prototypes up quickly and then grow them. Then Java arrived and sucked all of the air and mindshare out of the ecosystem. Java lucked into ideal circumstances, and Sun Marketing played their hand very well. The Web was just taking off, VCs were looking for something new and hot, publishers were looking for the next big thing, and programmers were looking for something that wasn't C++. Java looked familiar enough, cost nothing, had Garbage Collection and Interfaces (putting Gang of Four Patterns within reach of many), and let programmers keep their favorite tools and editors instead of adopting Smalltalk's strange model of doing everything in a (mostly) sealed environment.

goatinaboat 6y ago
Then Java arrived and sucked all of the air and mindshare out of the ecosystem. Java lucked into ideal circumstances, Not only that but Java was free and Smalltalk was $50k/seat. There was a chicken-and-egg problem, no one could learn Smalltalk unless their organisation had already committed to it. It sounds weird to say it now but Java won by grassroots adoption.
- twic 6y ago
  Also, you could share Java code, or entire libraries or applications, by posting some files on a website. You already had the files, and someone downloading them could use them straight away. To share Smalltalk code on a website, you would go through the file out / file in process, which was considerably clunkier. Also, i don't think Smalltalks of the time had namespaces, which also makes sharing code harder to get right. Java's reverse-DNS package naming is a surprisingly important innovation.
boris 6y ago
> There'd been a number of spectacular C++ project failures... And the most successful company of that era (Google) went ahead and implemented their product (the search engine) in C++...
- blihp 6y ago
  It's one thing when a tech company with lots of technical talent like Google decides to build its own (core) tools in a language like C++. It's another thing entirely when large numbers of IT departments, who have vastly more business than technical knowledge, try to build sprawling business applications in it. That's where most of the failures were occurring and why they were looking at Smalltalk, Java etc.
- dws 6y ago
  Years later. What later became Google was initially prototyped in Java and Python.
mardifoufs 6y ago
>There'd been a number of spectacular C++ project failures, Do you have any examples in mind? Big corporate software project failures are always super interesting imo. Especially those that happened during such pivotal times as rhe 1990s.
- chubot 6y ago
  I wasn't there, but apparently Taligent was a failed C++ operating system from Apple and IBM in the 90's. I think there is a talk on YouTube by Bryan Cantrill that gives some color on it... https://en.wikipedia.org/wiki/Taligent https://en.wikipedia.org/wiki/Taligent http://bobcongdon.net/blog/2004/06/the-taligent-effect/ http://bobcongdon.net/blog/2004/06/the-taligent-effect/
  - lou1306 6y ago
    The Digital Antiquarian also touches on Taligent in his post about the IBM/Apple "alliance" in the 90s: https://www.filfre.net/2020/02/the-deal-of-the-century-or-the-alliance-of-losers/ https://www.filfre.net/2020/02/the-deal-of-the-century-or-th...
  - protomyth 6y ago
    From Aaron Hillegass Cocoa® Programming for Mac® OS X, Third Edition Once upon a time, there was a company called Taligent, which was created by IBM and Apple to develop a set of tools and libraries like Cocoa. About the time Taligent reached the peak of its mindshare, I met one of its engineers at a trade show. I asked him to create a simple application for me: A window would appear with a button, and when the button was clicked, the words “Hello, World!” would appear in a text field. The engineer created a project and started subclassing madly: subclassing the window and the button and the event handler. Then he started generating code: dozens of lines to get the button and the text field onto the window. After 45 minutes, I had to leave. The app still did not work. That day, I knew that the company was doomed. A couple of years later, Taligent quietly closed its doors forever. It is asserted a bit later than C++ was the problem.
  - sgerenser 6y ago

by dws 6y ago

goatinaboat 6y ago

Then Java arrived and sucked all of the air and mindshare out of the ecosystem. Java lucked into ideal circumstances, Not only that but Java was free and Smalltalk was $50k/seat. There was a chicken-and-egg problem, no one could learn Smalltalk unless their organisation had already committed to it. It sounds weird to say it now but Java won by grassroots adoption.

twic 6y ago
Also, you could share Java code, or entire libraries or applications, by posting some files on a website. You already had the files, and someone downloading them could use them straight away. To share Smalltalk code on a website, you would go through the file out / file in process, which was considerably clunkier. Also, i don't think Smalltalks of the time had namespaces, which also makes sharing code harder to get right. Java's reverse-DNS package naming is a surprisingly important innovation.

boris 6y ago

> There'd been a number of spectacular C++ project failures... And the most successful company of that era (Google) went ahead and implemented their product (the search engine) in C++...

blihp 6y ago
It's one thing when a tech company with lots of technical talent like Google decides to build its own (core) tools in a language like C++. It's another thing entirely when large numbers of IT departments, who have vastly more business than technical knowledge, try to build sprawling business applications in it. That's where most of the failures were occurring and why they were looking at Smalltalk, Java etc.
dws 6y ago
Years later. What later became Google was initially prototyped in Java and Python.

mardifoufs 6y ago

>There'd been a number of spectacular C++ project failures, Do you have any examples in mind? Big corporate software project failures are always super interesting imo. Especially those that happened during such pivotal times as rhe 1990s.

chubot 6y ago
I wasn't there, but apparently Taligent was a failed C++ operating system from Apple and IBM in the 90's. I think there is a talk on YouTube by Bryan Cantrill that gives some color on it... https://en.wikipedia.org/wiki/Taligent https://en.wikipedia.org/wiki/Taligent http://bobcongdon.net/blog/2004/06/the-taligent-effect/ http://bobcongdon.net/blog/2004/06/the-taligent-effect/
- lou1306 6y ago
  The Digital Antiquarian also touches on Taligent in his post about the IBM/Apple "alliance" in the 90s: https://www.filfre.net/2020/02/the-deal-of-the-century-or-the-alliance-of-losers/ https://www.filfre.net/2020/02/the-deal-of-the-century-or-th...
- protomyth 6y ago
  From Aaron Hillegass Cocoa® Programming for Mac® OS X, Third Edition Once upon a time, there was a company called Taligent, which was created by IBM and Apple to develop a set of tools and libraries like Cocoa. About the time Taligent reached the peak of its mindshare, I met one of its engineers at a trade show. I asked him to create a simple application for me: A window would appear with a button, and when the button was clicked, the words “Hello, World!” would appear in a text field. The engineer created a project and started subclassing madly: subclassing the window and the button and the event handler. Then he started generating code: dozens of lines to get the button and the text field onto the window. After 45 minutes, I had to leave. The app still did not work. That day, I knew that the company was doomed. A couple of years later, Taligent quietly closed its doors forever. It is asserted a bit later than C++ was the problem.
- sgerenser 6y ago