LISP is hard to read, here's some actual reasons and a decently researched blog post
vs
nuh-uh, it's easy to read
David Hagerty
@dathagerty.com
255 followers 819 following 676 posts
I write C# and Rust to make restaurant do smart and be CRDT I've been paid to productionize k8s crimes They/them Husband, dad, hobby desirer
![A slightly more readable form of the code in this image is as follows:
```
# Dynamic method generation via LLM for *every* Ruby object.
class Object
# Intercept unknown messages, ask an LLM for the body, define & cache.
def method_missing(name,*args,**kw,&blk)
(@__dyn ||= {})[name]&.then { |m| return m.call(*args,**kw,&blk) }
state = instance_variables.reject { |v| v == :@__dyn }
.map { |v| [v, instance_variable_get(v)] }
.to_h
prompt = <<~PROMPT
You are an expert Ruby dev.
Write body for #{name} given args=#{args.inspect} kw=#{kw.inspect}
and state=#{state.inspect}. Return body only.
PROMPT
raise "@llm must respond to #complete" unless @llm&.respond_to?(:complete)
body = @llm.complete(prompt).strip
self.class.class_eval("def #{name}(*a,**k,&b)\n#{body}\nend", __FILE__, __LINE__)
(@__dyn[name] = method(name).to_proc).call(*args,**kw,&blk)
end
def respond_to_missing?(name, include_private = false)
(@__dyn && @__dyn.key?(name)) || super
end
end
```](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:bjaceaxgoto5p7gor2rcov3g/bafkreiewxub3li6rschy52avuj6agwbqdivbfegcz57tz3uqf3rawoep2m)
