The Lisp curse, now coming to your ecosystem

Re:The Lisp curse, now coming to your ecosystem by Xirdus on Thursday November 05, 2026 @05:39PM (#50385518)

Is there any such syntax remaining? Sure, 20 years ago it was a pain to do manipulations of more than 1 element at a time. But nowadays everyone and their dog has some form of iterator combinators that make it a one liner. Even C++, although the line gets quite wide. Is there anything that, as of 2026, you miss having in your day job language (and that language isn't Java)?

[ Parent | on HN ]

Re:The Lisp curse, now coming to your ecosystem by brlewis on Thursday November 05, 2026 @08:32PM (#50387040)

I'm having fun in TypeScript and only casually missing the capabilities of macros. It's Turing-complete, so doing the equivalent things is a simple matter of programming. And I'm almost always processing JSON structures, not SQL result rows, so I don't miss being able to write syntax like `sql-repeat` on a day-to-day basis.

[ Parent | on HN ]

Re:The Lisp curse, now coming to your ecosystem by Xirdus on Thursday November 05, 2026 @10:02PM (#50387638)

Languages are no more Turing-complete than they were 50 years ago. If lack of Lisp macros was such a huge deal back then it affected day to day web development, then surely it must be affecting us all in this day and age too. Arguably, using JSON instead of SQL should make such macros even more important due to the unnesting of data we need to do. So why isn't it?

[ Parent | on HN ]

Re:The Lisp curse, now coming to your ecosystem by brlewis on Friday November 06, 2026 @10:13AM (#50393306)

About today, JavaScript is good at referencing JSON. You don't need macros to make it better at it.

About back then, Perl/PHP/Python/Java/Ruby were never as good at pulling groups out of rows of SQL, but people could work around that by taking more time, writing more code, being more careful. So if you haven't seen macros used to make it better, you don't realize you're missing out on a huge deal. Maybe you just have a vague idea that things could be better, but you're too busy finding and fixing bugs to pursue this thought.

[ Parent | on HN ]

Re:The Lisp curse, now coming to your ecosystem by Xirdus on Friday November 06, 2026 @11:45AM (#50394770)

In other words, as of 2026, this phrase:

> if what you mean is, you haven't seen macros used in ways that make you wish your day-job programming language had macros, that's fixable.

is not true at all anymore? Or is it only true under very specific circumstances (if so, what are they)?

[ Parent | on HN ]

Re:The Lisp curse, now coming to your ecosystem by brlewis on Friday November 06, 2026 @03:40PM (#50398191)

True if you would like syntax that doesn't lend itself to eager evaluation. In the `sql-repeat` example, `group-beginning?` takes an expression that can't be eagerly evaluated. It's evaluated twice, once for the current row and once for the previous row, and the result of evaluation is compared. It can't just be eagerly evaluated for the current row and the result used.

Also true if you want a shorthand syntax for defining a variable where the name of the variable is meaningful. JavaScript takes care of the most common case with destructuring assignment, but with macros you could make such syntax yourself.

[ Parent | on HN ]