41–50 of 193 posts
I really wish this book used something other than Java. Nothing against Java - just that I don't know it and don't feel excited about learning it.
For what it's worth, these days you could use an LLM to turn each code snippet into many other languages. Or just focus on his words and use the snippets like generic code and figure out how to do it in whatever language of choice. You don't need to "learn java" to become conversant or read it as pseudocode.
I really wish this book used something other than Java. Nothing against Java - just that I don't know it and don't feel excited about learning it.
I really wish this book used something other than Java. Nothing against Java - just that I don't know it and don't feel excited about learning it.
Mad respect to those with that kind of dedication, and everyone working to keep all the dev infrastructure going, but I'm super glad my "I want to make a language" phase was just a passing interest! That's just a crazy amount of work!
I really wish this book used something other than Java. Nothing against Java - just that I don't know it and don't feel excited about learning it.
When Java gets pattern matching, it will become a more reasonable choice to write an interpreter in.
Alright, I will finally read the book. It has been collecting dust in my bookshelf for a while.
Mad respect to those with that kind of dedication, and everyone working to keep all the dev infrastructure going, but I'm super glad my "I want to make a language" phase was just a passing interest! That's just a crazy amount of work!
It doesn't have to be a crazy amount of work, see Lisp-in-Lisp in the original SCIP book or a lambda calculus interpreter in Haskell (fits on a screen).
I guess if you have a lot of fairly small ideas with a lot of novelty, I could see the appeal of a new language to express them in.
Mad respect to those with that kind of dedication, and everyone working to keep all the dev infrastructure going, but I'm super glad my "I want to make a language" phase was just a passing interest! That's just a crazy amount of work!
It doesn't have to be a crazy amount of work, see Lisp-in-Lisp in the original SCIP book or a lambda calculus interpreter in Haskell (fits on a screen).
You could spend considerably more time implementing a Lisp dialect's math library than the interpreter. There are a lot of combinations.
Where are the objects, hash tables, exception handling, ...
Of course you can get some of these things from a host language, but someone had to make them.
Is this book still relevant?