Hacker News: lgrapenthin

New comment by lgrapenthin in "My thoughts after using Clojure for about a month"

lgrapenthin — Wed, 03 Jun 2026 02:14:02 +0000

"As a rule of thumb, if your application never has 10,000 virtual threads or more, it is unlikely to benefit from virtual threads."

https://docs.oracle.com/en/java/javase/21/core/virtual-threa...

New comment by lgrapenthin in "My thoughts after using Clojure for about a month"

lgrapenthin — Wed, 03 Jun 2026 02:08:47 +0000

Clojure is about its rigorous and pragmatic "immutability first" paradigm that you simply don't get from other PLs.

LISP is much more than just a runtime syntax, such as its distinct evaluation model and metalinguistic core.

The JVM was chosen for Clojure because of its reach and vast ecosystem. People have ported Clojure to other runtimes, even Beam (Clojerl), where it enjoys decent success, too.

New comment by lgrapenthin in "I'm Tired of Talking to AI"

lgrapenthin — Wed, 27 May 2026 17:51:59 +0000

Why does this read like written by AI?

New comment by lgrapenthin in "We stopped AI bot spam in our GitHub repo using Git's –author flag"

lgrapenthin — Mon, 18 May 2026 16:30:16 +0000

What you are describing is exactly a security implication.

New comment by lgrapenthin in "Clojurists Together – Q2 2026 Open Source Funding Announcement"

lgrapenthin — Tue, 05 May 2026 10:16:15 +0000

Might be some personal beef, but I don't know really and don't care enough. He makes these authorative claims mixed with personal sentiment and then doesn't back them up.

Here for instance the core team supposedly has "lost control of the compiler" https://x.com/dustingetz/status/1947643515480965346

Work on the compiler had been pushed a month earlier https://github.com/clojure/clojure/commit/6a3e0f02c6a96fcef2...

New comment by lgrapenthin in "Clojurists Together – Q2 2026 Open Source Funding Announcement"

lgrapenthin — Tue, 05 May 2026 00:18:20 +0000

Of course calling out baseless FUD is helpful. Otherwise it just discourages people from engaging with Clojure, which is not helpful.

New comment by lgrapenthin in "Clojurists Together – Q2 2026 Open Source Funding Announcement"

lgrapenthin — Mon, 04 May 2026 11:14:06 +0000

There is no falling apart. This guy just tries to spread this narrative every two months or so, idky. Check out latest dev call https://www.youtube.com/watch?v=ngyvDkZA3o0

New comment by lgrapenthin in "Agentic Coding Is a Trap"

lgrapenthin — Mon, 04 May 2026 02:29:47 +0000

Indeed. Generated code is also harder to read because it violates all semantic expectations that rely on the mental model of a human author. A generated piece of code is linguistically plausible but often unknowingly imitates common idioms so incoherently that the actual bug may be accidentally disguised in a way no sane human (even a bad programmer) could have come up with.

Since LLMs have no internal evaluation, as a reviewer one has to account for it and evaluate line by line, rebuild from scratch any hidden rationale and tacit knowledge the LLM didn't have in the first place - only to be mislead into non concerns draining costly hours.

At this point, the investment is often deeper than writing from scratch.

New comment by lgrapenthin in "Why I still reach for Lisp and Scheme instead of Haskell"

lgrapenthin — Thu, 30 Apr 2026 13:36:10 +0000

In Clojure

    true: true
    false: false
    null: nil
    []: []
    {}: {}

New comment by lgrapenthin in "System Card: Claude Mythos Preview [pdf]"

lgrapenthin — Wed, 08 Apr 2026 19:00:37 +0000

They are just trying to peddle their "It's alive" headlines.

Text generators mostly generate the text their are trained and asked to generate, and asking it to run a vending machine, having it write blog posts under fictional living computer identity, or now calling it "Mythos" - its all just marketing.

New comment by lgrapenthin in "Common Lisp Screenshots: today's CL applications in action"

lgrapenthin — Sat, 14 Feb 2026 16:25:56 +0000

Assuming that everybody disagreeing with such takes simply can't have tried the latest generator is quite telling. Consider, that maybe, I'm not as easily impressed?

New comment by lgrapenthin in "Common Lisp Screenshots: today's CL applications in action"

lgrapenthin — Sat, 14 Feb 2026 06:43:43 +0000

My hammer is also solving problems. Still, hammering is not programming. LLMs are text generators.

New comment by lgrapenthin in "Common Lisp Screenshots: today's CL applications in action"

lgrapenthin — Sat, 14 Feb 2026 04:08:55 +0000

You are comparing a PL to a text generator. What are you on?

New comment by lgrapenthin in "Ex-GitHub CEO launches a new developer platform for AI agents"

lgrapenthin — Wed, 11 Feb 2026 18:07:37 +0000

The negativity is driven by outrageous claims how AIs will replace programmers, or how english is the PL of the future. T

New comment by lgrapenthin in "AI isn't "just predicting the next word" anymore"

lgrapenthin — Wed, 14 Jan 2026 00:22:07 +0000

Its generating an approximation of what it was trained on. Call it whatever you want, just not AGI or the road to AGI.

New comment by lgrapenthin in "Scott Adams has died"

lgrapenthin — Tue, 13 Jan 2026 19:26:06 +0000

How brave of you

New comment by lgrapenthin in "AI URI Scheme – Internet-Draft"

lgrapenthin — Tue, 16 Dec 2025 20:35:40 +0000

There is a newer version here https://datatracker.ietf.org/doc/draft-sogomonian-aiip-archi...

I don't understand what problem this is trying to solve though.

New comment by lgrapenthin in "Mistral releases Devstral2 and Mistral Vibe CLI"

lgrapenthin — Wed, 10 Dec 2025 18:01:04 +0000

I tried this on a small Clojure codebase and asked it to write some tests. It couldn't get its parentheses balanced. After 10 attempts or so it tried to write a smaller test file first, but again failed. Regardless of the parentheses, the test code it came up with was quite basic and arbitrary. It didn't try to come up with interesting edge cases or anything.

New comment by lgrapenthin in "The lost cause of the Lisp machines"

lgrapenthin — Thu, 20 Nov 2025 13:51:04 +0000

To me, it was never about the hardware. It was not even about LISP. It is about "clean design" and what a great computing environment was capable of, and still would be, had its potential not been shredded by the advent of cheap addicting hardware combined with an "operating system" so "simple and elegant" that even today, a program simply segfaults leaving you with nothing (instead of showing at least an inspectable stacktrace). So "simple and elegant" that the only two data formats end users are dealing with are "copy & paste text", "files", and "screenshots". An operating system so "pure" that every program lives in its own uninteroperable walled garden, that understands nothing about the environment and data loaded around it. We lost a whole computing world and it might still take ages getting that back.

New comment by lgrapenthin in "Transducer: Composition, abstraction, performance (2018)"

lgrapenthin — Sat, 08 Nov 2025 15:09:08 +0000

A transducer transforms a reducing function. Its signature is rfn->rfn. The resulting rfn can then be used to reduce/fold from any collection/stream type into any other collection/stream type.

I don't see what your functions have to do with that.