To add to this, I definitely wouldn't say we've converged on a set of languages in general either! Most of my backends are written in Scala of all things, and LLMs have no issue with it. If anything, the expressive type system is helpful for them.
> To add to this, I definitely wouldn't say we've converged on a set of languages in general either!
Absolutely agree. I’d take a guess that a decent chunk, if not majority of “business” applications probably still exist in either Django or Spring Boot. Should all of those be rewritten now “just ‘cause”?
If someone posts a story about topic Y and a reply is "does anyone really care about topic Y?" I would expect it to be flagged and downvoted.
The answer is "yes". Obviously people still care. No need to resurrect a dead bad post.
OP is apparently working on a new language and would like some assurance that someone out there might take an interest in it someday. That doesn't sound unreasonable to me.
so-cal-schemer attempted to bypass HN moderation by reposting a flagged post in its entirety without waiting for the "vouch" process to complete.
Meanwhile, behnamoh's post was essentially dismissing the idea that we should discuss non-AI topics in the age of AI. His mention of his hobby project doesn't redeem a garbage comment.
Have you found LLMs to be good at metalinguistic abstraction? I have used them a little bit for lisp programming but never once have I seen them introduce macro.
I'd imagine they would require some hands-on guidance to create more meaningful abstractions and DSLs for humans.
Call it "vibe coding by tiller". Ha.
Also, I think of metalinguistic abstraction as something deeper than macros. At least not limited to macros:
"An important advantage of making the evaluator accessible as a Lisp program is that we can implement alternative evaluation rules by describing these as modifications to the evaluator program."
LLMs are able to write racket. I have a fairly large project I've been vibecoding for the last 6 months. Models predating deepseek flash 0731 used to make paren mistakes and had a hard time. But now Opus 5.5 for example does not make any mistake writing clear racket code.
Well, taking it to extreme why care about any other than machine code?
As AI programming tools improve, we will have the second coming from what 4 GLs, RUP, CASE tools, and Japan's Fifth Generation Computer Systems were trying to achieve, each on its own way as the next evolution on programming abstractions.
so-cal-schemer · · focus · HN ↗
[dead]
BoxOfRain · · focus · HN ↗
msdz · · focus · HN ↗
Absolutely agree. I’d take a guess that a decent chunk, if not majority of “business” applications probably still exist in either Django or Spring Boot. Should all of those be rewritten now “just ‘cause”?
WolfeReader · · focus · HN ↗
The answer is "yes". Obviously people still care. No need to resurrect a dead bad post.
xhevahir · · focus · HN ↗
[deleted] · · focus · HN ↗
[deleted]
[deleted] · · focus · HN ↗
[deleted]
WolfeReader · · focus · HN ↗
Meanwhile, behnamoh's post was essentially dismissing the idea that we should discuss non-AI topics in the age of AI. His mention of his hobby project doesn't redeem a garbage comment.
[deleted] · · focus · HN ↗
[deleted]
amelius · · focus · HN ↗
vzcx · · focus · HN ↗
terminalcommand · · focus · HN ↗
so-cal-schemer · · focus · HN ↗
Call it "vibe coding by tiller". Ha.
Also, I think of metalinguistic abstraction as something deeper than macros. At least not limited to macros:
"An important advantage of making the evaluator accessible as a Lisp program is that we can implement alternative evaluation rules by describing these as modifications to the evaluator program."
<a href="https://sarabander.github.io/sicp/html/Chapter-4.xhtml" rel="nofollow">https://sarabander.github.io/sicp/html/Chapter-4.xhtml
ironqcold · · focus · HN ↗
terminalcommand · · focus · HN ↗
pjmlp · · focus · HN ↗
As AI programming tools improve, we will have the second coming from what 4 GLs, RUP, CASE tools, and Japan's Fifth Generation Computer Systems were trying to achieve, each on its own way as the next evolution on programming abstractions.