Time to dig up a classic story about Tom Knight, who designed the first prototype of the Lisp Machine at MIT in the mid-70's. It's in the form of a classic Zen koan. This copy comes from https://jargondb.org/some_ai_koans but I've seen plenty of variations floating around. A novice was trying to fix a broken Lisp machine by turning the power off and on. Knight, seeing what the student was doing, spoke sternly: “You c…
The lost cause of the Lisp machines
11–20 of 176 posts
Re: The lost cause of the Lisp machines
#12Re: The lost cause of the Lisp machines
#13Symbolics’ big fumble was thinking their CPU was their special sauce for way too long. They showed signs that some people there understood that their development environment was it, but it obviously never fully got through to decision-makers: They had CLOE, a 386 PC deployment story in partnership with Gold Hill, but they’d have been far better served by acquiring Gold Hill and porting Genera to the 386 PC architectu…
For those unaware, Symbolics eventually "pivoted" to DEC Alpha, a supposedly "open" architecture, which is how Genera became Open Genera, like OpenVMS. (And still, like OpenVMS, heavily proprietary.)
Re: The lost cause of the Lisp machines
#14Re: The lost cause of the Lisp machines
#15“ I am just really bored by Lisp Machine romantics at this point: they should go away. I expect they never will.” What? They’re awesome. They present a vision of the future that never happened. And I don’t think anyone serious expects lisp machines to come back btw.
Hauntology strikes again
Re: The lost cause of the Lisp machines
#16Symbolics’ big fumble was thinking their CPU was their special sauce for way too long. They showed signs that some people there understood that their development environment was it, but it obviously never fully got through to decision-makers: They had CLOE, a 386 PC deployment story in partnership with Gold Hill, but they’d have been far better served by acquiring Gold Hill and porting Genera to the 386 PC architectu…
For those unaware, Symbolics eventually "pivoted" to DEC Alpha, a supposedly "open" architecture, which is how Genera became Open Genera, like OpenVMS. (And still, like OpenVMS, heavily proprietary.)
Re: The lost cause of the Lisp machines
#17“ I am just really bored by Lisp Machine romantics at this point: they should go away. I expect they never will.” What? They’re awesome. They present a vision of the future that never happened. And I don’t think anyone serious expects lisp machines to come back btw.
Amiga romantics.
8-bit romantics.
PDP-10 romantics.
Let them stay. Let them romantizice.
Re: The lost cause of the Lisp machines
#18Earlier quoted context omitted.
I'm honestly surprised nobody tried to capitalize on the early 2000s Java hype by making some kind of Java box (there were a few things labeled as a Java OS or a Java workstation but none of these were really a "Java Machine")
Sun JavaStation: https://en.wikipedia.org/wiki/JavaStation
Re: The lost cause of the Lisp machines
#19The hardware was not very good. Too much wire wrap and slow, arrogant maintenance.
I once had a discussion with the developers of Franz LISP. The way it worked was that it compiled LISP source files and produced .obj files. But instead of linking them into an executable, you had to load them into a run-time environment. So I asked, "could you put the run time environment in another .obj file, so you just link the entire program and get a standalone executable"? "Why would you want to do that?" "So we could ship a product." This was an alien concept to them.
So was managing LISP files with source control, like everything else. LISP gurus were supposed to hack.
And, in the end, 1980s "AI" technology didn't do enough to justify that hardware.
Re: The lost cause of the Lisp machines
#20Earlier quoted context omitted.
Sun JavaStation: https://en.wikipedia.org/wiki/JavaStation
I was aware of these, it's kinda what I meant by "None of these were really Java Machines". They were just shitty sparc machines that had Java OS in flash. It didn't have some kind of Java co-processor and still relied on a JVM. Java OS was pretty neat but I wouldn't really consider it a "Java OS" since it was basically just a microkernel that bootstrapped a JVM from what I've read. An actual Java machine IMO would h…