The LISP 2 Project (2017)
ieeexplore.ieee.org
The LISP 2 Project (2017)
1–10 of 15 posts
Re: The LISP 2 Project (2017)
#2Re: The LISP 2 Project (2017)
#3[dead]
Re: The LISP 2 Project (2017)
#4The actual LISP 2 project to update LISP 1.5 (also conceptually, for example with a new syntax) was done in the mid 1960s. It was famous for its failure.
From 2017 is the work done to collect historical documents, source code, etc. about the LISP 2 project.
Re: The LISP 2 Project (2017)
#5Lisp with Algol-like syntax was of course Mulisp (1977). It was so beautiful and complete that it was end of history. Everything else thereafter is just endless recycling same old shit. When you have clear rules between these two forms, you can implement macros effectively. Algol-programming department need not do macros anyway, because they are too stupid.
Re: The LISP 2 Project (2017)
#6An entertaining read. The technical reason why LISP 2 failed was the limited memory (42K) of the Q32, but there seems to have been fundamental issues in the conception of the language.
> Even if the project had had more mature leadership, it probably could not have overcome the unfortunate choice of an ALGOL-like syntax and type system, overemphasis on compiled code efficiency, and the obscure choice of first machine to build for.. LISP’s fundamental strengths were lost in LISP 2’s design.
Re: The LISP 2 Project (2017)
#7Lisp with Algol-like syntax was of course Mulisp (1977). It was so beautiful and complete that it was end of history. Everything else thereafter is just endless recycling same old shit. When you have clear rules between these two forms, you can implement macros effectively. Algol-programming department need not do macros anyway, because they are too stupid. http://www.edm2.com/index.php/MuLISP
(hello, you are one of the people that have greatly inspired me many years go!
in the early hackerspace days there was a lot of talk of diy, but it was a kind of consumer lifestyle thing, like stitching a new strap to your laptop backpack. I think the accounts of your projects, and your adventures, put me in the direction of thinking of diy as not some kind of external activity, but as the default mode of living. solving problems from first principles, refining them from experience, solving your own problems with solutions that are fundamentally superior to off the shelf consumer stuff, because they are driven by your own needs and knowledge and experience.
my vessel of choice is a dinghy, and it's built from a kit, and the waters I navigate are much gentler than yours, but everything else is diy and jury rigged, and I sometimes would say some solution is "in the spirit of timonoko", and sometimes people ask "who's timonoko" and I say "oh it's this crazy cool Finnish kayaking guy, he wrote his own navigation software from first principles, and he wrote his own lisp, and he got into all kinds of amazing kayaking adventures"
so, thank you!)
Re: The LISP 2 Project (2017)
#8Lisp with Algol-like syntax was of course Mulisp (1977). It was so beautiful and complete that it was end of history. Everything else thereafter is just endless recycling same old shit. When you have clear rules between these two forms, you can implement macros effectively. Algol-programming department need not do macros anyway, because they are too stupid. http://www.edm2.com/index.php/MuLISP
(hello, you are one of the people that have greatly inspired me many years go! in the early hackerspace days there was a lot of talk of diy, but it was a kind of consumer lifestyle thing, like stitching a new strap to your laptop backpack. I think the accounts of your projects, and your adventures, put me in the direction of thinking of diy as not some kind of external activity, but as the default mode of living. sol…
This is the way.
Re: The LISP 2 Project (2017)
#9Lisp with Algol-like syntax was of course Mulisp (1977). It was so beautiful and complete that it was end of history. Everything else thereafter is just endless recycling same old shit. When you have clear rules between these two forms, you can implement macros effectively. Algol-programming department need not do macros anyway, because they are too stupid. http://www.edm2.com/index.php/MuLISP
This looks like the implementation:
https://github.com/jlfaucher/FormMath/blob/master/SRC/MUSIMP...
Curiously, the comments are in French.
Re: The LISP 2 Project (2017)
#10See also https://www.softwarepreservation.org/projects/LISP/lisp2_fam... .
(Author of _Annals_ paper here.)