Unrelated to Wren, but I felt that Bob's book "Game Programming Patterns" ([1] and a free web version [2]) was excellent, and a very down to earth treatment of the topic. All of the examples were relevant and pretty hard hitting.

I know patterns (especially "design patterns") have become a bit of a swear-word, something which hints at severe engineering malpractices, especially along the lines of introducing unnecessary complexity for seemingly its own sake. I think that view oversimplifies the topic greatly, so hopefully people don't dismiss it at face value.

[1] http://gameprogrammingpatterns.com/ [2] http://gameprogrammingpatterns.com/contents.html

GPP was great. Plus, Bob's new book is about writing interpreters!

http://craftinginterpreters.com/

Ah cool, thanks for the link.

It sounds like it may actually come in handy - I've ended up creating a number of solutions which came pretty close to being fully fledged domain specific languages. Sadly, despite nominally passing a CS compilers course about 20 years ago, my implementations have been horrifically incorrect. Maybe it's time to refresh my memory of how to actually do this.

oh nice, yea it's coming along (the book is not complete yet, like before, it's written and each chapter put up when complete). There's a github repo as well.

I'd say it's worth the fun of writing your own alongside or after!

The dev logs typically go into detail on the decisions I make, for the decision on wren see https://luxeengine.com/dev-log-5/ .

Nice, I really like this!

thanks :)

Looks like a neat little language. Lua's syntax always appeared ugly to me - or if not ugly, then unnecessarily foreign. Something more Javascript-like lowers that barrier a good bit.

Doing source transformation "transpiling" from something more Javascript like to Lua has always been trivial.

Not that Lua is ugly (subjective), I find it as something Javascript should have always been.