frollogaston

They're on a dedicated VLAN in the county dump

That's some of it too, but in a way legs aren't all that different from wheels in how they work. Most of it is the gearing. Like there's a gear on every mountain bike that will make your feet go down at the same intervals as walking. That sucks on flat terrain. Legs are also not perfectly designed to push pedals, especially for people who don't bike often.

Like asn1, relational DB drivers, Redis, protobuf, XML/YAML/JSON parsing, web client/server, and SDKs for stuff like AWS. Not saying Common Lisp lacks well-maintained versions of those, cause I don't know, just that those are the foundational things I wouldn't want LLM-coded.

But every language lets you do this in development. Doing it in prod and hot reloading is Common Lisp's special feature.

Maybe beside the point, but I'd hope it's neither connection per process or per thread. Modern webservers tend to rely on either an event loop or greenthreading. Looks like such a thing exists in Common Lisp, not sure how the debugger would interact with it though.

Anyway it sounds like this isn't really the target use case for the debugger since restarting a webserver is supposed to be easy. Maybe there's a different use case in mind?

I think that too favors walking the bike up the incline. Anyone able-bodied should be able to do it, some faster than others, but biking up an SF incline is more hit or miss, especially when considering different bikes.

My reasoning for the bike-hike being faster is that legs are designed for it. Legs are only inefficient on flatter ground because you have no equivalent of high gear (like extendible legs), so all that torque is going to waste.

Erm, sounds niche. Like you can normally do all that minus resuming the program in other languages. If this is a webserver, it should be fine to restart it for an update, it's not like I'm going to catch some user's failed request and patch it before it times out.

Yeah, I'll use LLMs to write all application code, but not so sure about libraries. Especially more foundational ones.

This looks like a good debugger, but it's similar to ones I've used in other languages. What's special about this one? I thought the idea was you use the debugger in prod, but now I don't think that's what the article meant.

Was assuming it was a backend. I still don't understand the advantage though. It'd help to have an example.

Yeah but what happens to your server then? The connection it was handling times out I guess, then is the rest of it frozen or what?

IF you're running a debug build. I guess Common Lisp can do this in prod?

  Also, in most languages an error will crash your program. So if you’re writing code with an LLM it will have to read your crash logs to make some changes and run your program again. In Common Lisp your program won’t crash, it’ll stop and open a debugger with the whole stack and all the variables. You can just point your LLM at the debugger, and it’ll make its fix and resume the program.

What does this look like in a real example system that you're maintaining? I can't imagine you'd always be able to resume like that if it's something like a webserver.