See also part 2 https://norvig.com/lispy2.html
Gemini did write Lisp-1 interpreter in Linux-assembly the other day. It was ready to implement garbage collection and compiler and all shit, but that was just depressing from human point of view.
just because someone or something else does it better?
If all you care about is the artifact and not the path, there is no reason to do anything.
Use the tool to better yourself, your understanding and push the limits of what is possible. If an Lisp in assembly with GC is now hello world, change what a hard project is.
I see this attitude a lot, and I think it is rooted in a sort of self-centered elitism. Anyone can do it, so why do it? Instead you could have the AI teach you how to implement it yourself with a deep understanding that no human, even if you paid them, would put up with.
But sure, get depressed. But why tho?
I don't think a good learning resource gets worse just because there's a newer alternative.
tosh•1h ago
Illuminating experience and it will also help you see (among many other things) the parentheses in a different light.
stdatomic•1h ago
Needless to say that was my opinion and every day I think, more and more, how right he was.
(later I did make some gui apps that included scripting and chose s-expr syntax because of how simple it is to implement it)
NooneAtAll3•1h ago
had brackets been displayed as curly braces in C - everything would look much more manageable
phpnode•46m ago
irishcoffee•26m ago
eska•40m ago
bananaflag•1h ago
1) Humans are not that equipped to handle that level of nesting without some other aid, this is why Lisp code is usually indented.
2) Parentheses aren't just about grouping, and this is unintuitive. For example, x is not the same as (x). This is a bit like in set theory where x is not the same as {x}, but parentheses do not look like the kind of sign that would work like that.