Live data from Hacker News

Why Lisp?

nyxt.atlas.engineer

11–20 of 339 posts

Re: Why Lisp?

#13

> On the other hand, Lisp code written some 30 years ago will most of the time, without issue, work on a modern Common Lisp implementation. Yeah, just like Perl. Or Latin. No one uses them, these are dead languages that belong to a museum. It can be fun to study them and you definitely should if you want to be well-educated and know the history behind the modern world, but that's it.

Arm, AMD, and Intel are using a Common Lisp application called ACL2 to formally verify their main products. Google Flights' core is written in Common Lisp. It's far from dead.

Re: Why Lisp?

#15
post #8

> When you have a running program you can compile functions, redefine classes, etc. all while the program is running. You are changing the internal state of the image. This can surely be convenient in certain cases, however most of the times I find myself playing around with unit tests rather than with a single running process. Unit tests are small and fast so I don't even notice any inconvenience with the traditiona…

I work with clojure and test driven development is not nearly as productive as repl driven development imo.

Re: Why Lisp?

#16
post #4

> and then they say "this language is Turing complete and therefore should be able to do anything you want it to do." i'm pretty sure that no designers of modern languages would say anything as naive as that. > sible in Lisp was the implementation of an object oriented programming system without having to change the compiler! haven't people done that using C? > This meant that all code written in Python 2 could not b…

> not all python 2 code could be directly "leveraged", but it certainly could be translated, and has been

translating is an effort. running lisp code thats 30 years old is mostly a matter of pressing play

> don't get me wrong - i like lisp, but this article would not convince me if i was thinking of coming to it as a newbie

given that this is more of a "tweet" than an article i think you missed the point

Re: Why Lisp?

#17
post #8

> When you have a running program you can compile functions, redefine classes, etc. all while the program is running. You are changing the internal state of the image. This can surely be convenient in certain cases, however most of the times I find myself playing around with unit tests rather than with a single running process. Unit tests are small and fast so I don't even notice any inconvenience with the traditiona…

I work with clojure and test driven development is not nearly as productive as repl driven development imo.

I'll have to agree here, with the caveat that this applies to functional code.

For side-effect heavy code, a repl is not nearly as productive as good tests and a debugger.

(What is interesting is that people tend not to test or check manually their code's side effects, so a repl is the best option for almost all the debugging that people actually do.)

Re: Why Lisp?

#19
post #4

> and then they say "this language is Turing complete and therefore should be able to do anything you want it to do." i'm pretty sure that no designers of modern languages would say anything as naive as that. > sible in Lisp was the implementation of an object oriented programming system without having to change the compiler! haven't people done that using C? > This meant that all code written in Python 2 could not b…

> not all python 2 code could be directly "leveraged", but it certainly could be translated, and has been translating is an effort. running lisp code thats 30 years old is mostly a matter of pressing play > don't get me wrong - i like lisp, but this article would not convince me if i was thinking of coming to it as a newbie given that this is more of a "tweet" than an article i think you missed the point

> given that this is more of a "tweet" than an article i think you missed the point

this wasn't posted on twitter. but if you mean it was short and of poor content, then i agree with you.

Post reply on HN