Hacker News new | past | comments | ask | show | jobs | submit login

realistically, it's the REPL, not the editor, that makes lisp what it is - not just having a repl running, but to have your app be part of the repl, and you develop it bit by bit.

The javascript/UI people have found live reloading/editing to be a game changer, but this has been the case for lisp development since...well, the beginning!




Live reloading (recompiling per method, editing values in your live runtime image) has been with UI development since since the beginning of GUIs. Smalltalk is great.

The 90s with C++ and Java broke with history. Thankfully the rise of web apps has given us iteration speed back!


Kind of.

Visual Age for C++ inherited the Smalltalk experience, alongside Energize C++,provided a similar experience, but were too expensive for early 1990's hardware and too resource hungry.

Live++ brought the experience back to game developers.

Java has supported partial live reloading since early days, and for those willing to pay for it, JRebel takes the experience further, back to Lisp/Smalltalk.


First SmallTalk versions were built with Lisp. “Live environment” and “world image” were just inherited.


Actually, the first version of SmallTalk was implemented in BASIC! https://codersatwork.com/dan-ingalls




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: