sramsay

Yes. Or "Lisp for hardware nerds." ;)

I think what you're talking about is part of a much larger pattern. Autotools imagines that the most important thing is the "user" in a world where people want to download your software and build it on their machine. They don't care (as much) about fast build times, the semantic clarity of the build files themselves, the ease with which one may change or extend the build sequence, test harnesses . . . Those are all developer worries.

They do care that the code can compile on their (possibly old) machine. They do care about the ability to include some features and not others (including their ability to not have to make decisions on this if they don't want to). And they certainly want documentation that helps them to achieve their goal (which, again, is to build the software).

The newer tools make substantial inroads in making the developer's life easier. If your software is not of the sort where people download it and try to build it (because it only ships as a closed binary, is entirely internal, etc.) then maybe that makes sense. But until all these fancy gadgets start seriously caring about the use case above, I'm going to stick with autotools.

I do find that "signalling expertise" is important. "I have a significant background in biblical scholarship. You can assume I've read the most important works in NT studies in particular. Do not translate Greek, Latin, Hebrew, or Syriac. Now, I would like to know . . ." That changes things significantly. So does telling it you have 20+ years of experience with C programming, that you have a robust understanding of machine organization, memory layouts, embedded systems, etc.

I absolutely understand what you're saying. It makes complete sense. But I will never, ever shake the sense that software that isn't as fast as possible is offensive, immoral, delinquent -- the result of sloth, lassitude, lack of imagination, and a general hostility toward our noble Art.

"Fast enough" will always bug me. "Still ahead of network latency" will always sound like the dog ate your homework. I understand the perils of premature optimization, but not a refusal to optimize.

And I doubt I'm alone.

I'll put TB Barricade against Pro-L 2 and TB Reverb against Pro-R for sure. I mostly use other stuff for EQ and compression, but those two are really very similar to the FB offerings.

And honestly, if I was on a desert island with just u-he plugins . . .

This. Is. Awesome.

Really. It amazes me that I still find out about new Linux plugins after years of producing music on the platform. It could not have been easy to compile this; the information is all over the place online.

The ability to filter (!) for compression, saturation, etc. is so great.

Thank you!

Author, here. This is exactly the question I was trying (perhaps ineptly) to pose: If we designed a programming language with the idea that it would be primarily or exclusively vibe coded, what would that language look like? Might it look something more like Lean? Or more like theorem provers in general? Or would it look more like a natural language PL (think Inform 7)? Or what about a heavily declarative DSL like FAUST (for audio DSP)?

None of our existing programming languages were designed for quite the circumstance in which contemporary programming now finds itself; they all address an ergonomic situation in which there are humans and machines (not humans, machines, and LLMs).

It's possible, I suppose that the only PL that makes sense here is the one the LLMs "knows" best, but I sort of doubt that that makes sense over the long term. And I'm repeating myself, but really, it seems to me that a language that was written entirely for the ergonomic situation of human coders without any consideration of LLMs is not addressing the contemporary situation. This is not a precise analogy, but it seems to me a little like the difference between a language that was designed before vs after multicore -- or before vs after the internet.

There might be. And I certainly bear no ill will of any kind toward the project or its devs. But I am in terminals all day long, and I hesitate to use one that is written in a language that hasn't yet hit 1.0.

Foot is way more my speed. Fast, extremely stable, and (most importantly) barely noticed. When it comes to terminals, the slightest flicker -- the merest bug -- and I'm gone. And that happened to me with both ghostty and alacritty.

I keep hearing this, but I fail to see why "the massive, well-maintained set of critical libraries upon which UNIX is based" is not a good reason to use C in 2025.

I have never seen a language with a better ffi into C than C.

Truly, one of the most original artists of our time. I am among those who think Einstein on the Beach is one of the greatest theatrical works of the twentieth century, but I don't think I ever saw a Wilson piece that didn't completely blow my mind.

I seem to recall an interview in which he said that he didn't think many of his works should be revived. I hope that's not true, and that his pieces have a long life in repertory.

> I'm not a scholar, just an amateur, but two sentences were strikingly ridiculous.

Well, I am a scholar, and if you mean "Noah clearly did not hide these texts," then yes. Of course, that is ridiculous.

But it's actually a crucial bit of information if you're a humanist scholar. The article doesn't say anything about it, but the question would be: Which tradition recorded this legend about these texts? Almost any answer is important, because one culture trying to legitimate its own literary traditions or those of another through its own myths or those of another is absolute gold. It helps us to understand the way literary and religious syncretism unfolded (or failed to unfold) in the ancient near east and in later epochs . . .

I remember megatons of Java Servlet(tm) hype convincing us that real programmers do OO.

Java remains the only programming language I've ever heard covered in a feature story for NPR.