I have a suspicion that outside of the 10 people writing lisp seriously—shirakumo, stylewarning, lispm, and some others— there’s more characters of prose praising lisp being written than lisp being written. It’s a great language. I really like it and am using it for some projects. I just want people to actually use it rather than talking about using it. Edit: I’m wrong in the present case! Author has some cool projec…
(I've done a lot of Lisp, for money, and for open source platform&community buildout.) HN articles about exotic things, not just Lisp, do seem to get upvoted disproportionately. Also, PG declared Lisp as something you're supposed to think is important or a superpower, and I've wondered whether that also contributes to some upvotes on HN. But I'm not aware that a single one of the bajillion YC startups used Lisp. Mayb…
I still Lisp (2021)
51–60 of 119 posts
Re: I still Lisp (2021)
#52I have a suspicion that outside of the 10 people writing lisp seriously—shirakumo, stylewarning, lispm, and some others— there’s more characters of prose praising lisp being written than lisp being written. It’s a great language. I really like it and am using it for some projects. I just want people to actually use it rather than talking about using it. Edit: I’m wrong in the present case! Author has some cool projec…
I feel like there may be more Emacs Lisp being written recently than other Lisps and prose about Lisp combined.
Re: I still Lisp (2021)
#53I've been digging into Common Lisp again lately. I'm really enjoying some parts: CLIM is weird but interesting, and the fact that I'm basically developing inside a debugger makes testing and iterating on stuff pretty straightforward. On the other hand, library documentation frequently feels more like the programmer was making notes to himself rather than illustrating how the code might actually be used. I was also pr…
Re: I still Lisp (2021)
#54Earlier quoted context omitted.
I've found Calva for VS Code to be excellent, what do you think is missing there?
I tried Calva a lot and suggested it to my coworkers a while back (2017ish) and it was nothing but trouble. Cursive seemed to work pretty well, though.
Re: I still Lisp (2021)
#55Earlier quoted context omitted.
I feel like there may be more Emacs Lisp being written recently than other Lisps and prose about Lisp combined.
which is a terrible shame and a lesson. of the 10 or so lisp like languages i've used extensively, elisp is by far the worst. it succeeds because it interfaces with something important, and its carried along everywhere.
Re: I still Lisp (2021)
#56Earlier quoted context omitted.
This is the opposite of my experience: one of the main reasons I prefer to use Common Lisp and Clojure over any other language is that the tooling is so much better (emacs + SLIME [CL] or Cider [Clojure]). The only real competitors, imo, are SmallTalk and Prolog environments. However, part of this is the paradigm is completely different and it took me a bit of time to learn what made the tooling great.
Yeah, for Emacs users I'm sure Clojure is great. For the other 99% of us who use VS Code or IntelliJ or something else entirely, it really isn't. Though IntelliJ + Cursive I'd say is probably the best, it still pales in comparison to say Rust or TypeScript support in editors.
Re: I still Lisp (2021)
#57Earlier quoted context omitted.
(I've done a lot of Lisp, for money, and for open source platform&community buildout.) HN articles about exotic things, not just Lisp, do seem to get upvoted disproportionately. Also, PG declared Lisp as something you're supposed to think is important or a superpower, and I've wondered whether that also contributes to some upvotes on HN. But I'm not aware that a single one of the bajillion YC startups used Lisp. Mayb…
Lisp as a great tool for learning FP paradigms for application in other languages. IMO, in practice, the metaprogramming that Lisp encourages isn't very good good for the understandability of a codebase, which is IMO one of if not the most important factors for building an applications in a company .
Re: I still Lisp (2021)
#58I have a suspicion that outside of the 10 people writing lisp seriously—shirakumo, stylewarning, lispm, and some others— there’s more characters of prose praising lisp being written than lisp being written. It’s a great language. I really like it and am using it for some projects. I just want people to actually use it rather than talking about using it. Edit: I’m wrong in the present case! Author has some cool projec…
I'm happy to hear more thoughts and notes like this from the silent majority.
Re: I still Lisp (2021)
#59Earlier quoted context omitted.
I code in assembly in my mind. I just translate it to Lisp so others can understand it. (sarcasm over) If Lisp is so amazing, why does it not get more followers?
"If is so amazing, why doesn't everyone use it?" has got to be one of my least favorite questions. Never mind that it's lazy (in a bad way), it presupposes that people automatically adopt the best available technology or whatever, which is obviously false . But I think the thing that bothers me the most is that, asked with a different attitude and intent, it's usually a good question. E.g. Lisp is so much better than…
>I don't even use it, despite having such a near-worshipful attitude towards it.
How do you know that it is so much better then?
Re: I still Lisp (2021)
#60Earlier quoted context omitted.
I code in assembly in my mind. I just translate it to Lisp so others can understand it. (sarcasm over) If Lisp is so amazing, why does it not get more followers?
That you think assembly is fundamental rather than an accident of architecture really shows how undereducsted you are in computer science. Lisp isn't great because it's weird, it's great because it lucked into homoiconicity in its birth. It's weird because no other language family can do that. It's not popular because the majority of programmers are mediocre and will never understand the point of homoiconicity.