Live data from Hacker News

The lost cause of the Lisp machines

tfeb.org

31–40 of 176 posts

Re: The lost cause of the Lisp machines

#31
> I’d be saying that in a few years there are going to be a lot of huge farms of GPUs going very cheap if you can afford the power. People could be looking at whether those can be used for anything more interesting than the huge neural networks they were designed for.

Author falls into the same trap he talks about in the article. AI is not going away, we are not going back to the pre-AI world.

Re: The lost cause of the Lisp machines

#32
post #19

As someone who used Franz LISP on Sun workstations while someone else nearby used a Symbolics 3600 refrigerator-sized machine, I was never all that impressed with the LISP machine. The performance wasn't all that great. Initially garbage collection took 45 minutes, as it tried to garbage-collect paged-out code. Eventually that was fixed. The hardware was not very good. Too much wire wrap and slow, arrogant maintenanc…

> "So we could ship a product." This was an alien concept to them.

This mentality seems to have carried over to (most) modern FP stacks

Re: The lost cause of the Lisp machines

#33
post #4

“ 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.

See also: Amiga romantics. 8-bit romantics. PDP-10 romantics. Let them stay. Let them romantizice.

As an Amiga romantic, I’d say we have no illusions about a late-80s Amiga being a good idea if it existed today. But it captured my imagination (and at just the right age) like nothing else.

Re: The lost cause of the Lisp machines

#34
post #19

As someone who used Franz LISP on Sun workstations while someone else nearby used a Symbolics 3600 refrigerator-sized machine, I was never all that impressed with the LISP machine. The performance wasn't all that great. Initially garbage collection took 45 minutes, as it tried to garbage-collect paged-out code. Eventually that was fixed. The hardware was not very good. Too much wire wrap and slow, arrogant maintenanc…

Lisp Machines had versioning file systems IIRC. Kinda like on VMS. Was SCCS really that far ahead?

Re: The lost cause of the Lisp machines

#36
post #23

Earlier quoted context omitted.

Yes, but also. OpenGenera was ported to x86 some time ago.

I believe it's even been ported to the M1 a few years ago: https://x.com/gmpalter/status/1361855786603929601

Kinda sad seeing those follow-up tweets about licensing issues years later.

Re: The lost cause of the Lisp machines

#37
post #12
post #10

Earlier quoted context omitted.

And portacle.

Although Portacle isn't being maintained any more (at least as far as the main developer was concerned last time I looked a few months ago).

More information here:

https://github.com/portacle/portacle/issues/182

In 2020 they went full-time on developing the game Kandria.

They're still active:

https://shinmera.com/projects.html

https://shinmera.com/bio.html

Re: The lost cause of the Lisp machines

#38
post #19

As someone who used Franz LISP on Sun workstations while someone else nearby used a Symbolics 3600 refrigerator-sized machine, I was never all that impressed with the LISP machine. The performance wasn't all that great. Initially garbage collection took 45 minutes, as it tried to garbage-collect paged-out code. Eventually that was fixed. The hardware was not very good. Too much wire wrap and slow, arrogant maintenanc…

> "So we could ship a product." This was an alien concept to them. This mentality seems to have carried over to (most) modern FP stacks

Nah, it carried over to scripting languages.

Most of them still require a very specific, very special, very fragile environment to run, and require multiple tools and carefully ran steps just so it does same you can do with a compiled executable linked to the OS.

They weren't made for having libraries, or being packaged to run in multiple machines, or being distributed to customers to run in their own computers. Perhaps JS was the exception but only to the last part.

Sure it mostly works today, but a lot of people put a lot of the effort so we can keep shoving square pegs into round roles.

Re: The lost cause of the Lisp machines

#39

> I’d be saying that in a few years there are going to be a lot of huge farms of GPUs going very cheap if you can afford the power. People could be looking at whether those can be used for anything more interesting than the huge neural networks they were designed for. Author falls into the same trap he talks about in the article. AI is not going away, we are not going back to the pre-AI world.

AI will not go away, I agree. But many of the companies now betting the farm on AI are going to lose, and there will be server farms going for sale cheap. I'm hearing more and more people outside the tech world talk about the AI bubble, and predicting it's going to pop. When that happens and investors lose confidence, suddenly companies who need the next round of financing to pay off their current debts won't get it, and will go under.

I can't predict when the shakeout will be, but I can predict that not every AI company is going to survive when it happens. The ones that do survive will be the ones that found a viable niche people are willing to pay for, just as the dot-com bubble bursting didn't kill Paypal, eBay, and so on. But there are definitely going to be some companies going bankrupt, that's pretty clear even at this point.

Re: The lost cause of the Lisp machines

#40
post #19

As someone who used Franz LISP on Sun workstations while someone else nearby used a Symbolics 3600 refrigerator-sized machine, I was never all that impressed with the LISP machine. The performance wasn't all that great. Initially garbage collection took 45 minutes, as it tried to garbage-collect paged-out code. Eventually that was fixed. The hardware was not very good. Too much wire wrap and slow, arrogant maintenanc…

> "So we could ship a product." This was an alien concept to them. This mentality seems to have carried over to (most) modern FP stacks

Not the ones I've used. Haskell compiles to executables, F# compiles to the same bytecode that C# does and can be shipped the same way (including compiling to executables if you need to deploy to environments where you don't expect the .NET runtime to be already set up), Clojure compiles to .jar files and deploys just like other Java code, and so on.

I'll grant that there are plenty of languages that seemed designed for research and playing around with cool concepts rather than for shipping code, but the FP languages that I see getting the most buzz are all ones that can ship working code to users, so the end users can just run a standard .exe without needing to know how to set up a runtime.

Post reply on HN