Cool! This project started out as a way to learn Gr library routines in HolyC, and kind of Frankensteined its way into a game engine. In the coming weeks I'll be doing lots of refactoring to bring the code in line with proper TOS guidelines naming conventions.
(Author here: I cross-posted this comment from a reddit thread, hope it isn't against the rules..)
Can you comment on what the system's like to write for? i.e. development workflow, good/bad points about the language, things you thought were cool, things you thought weren't cool, that sort of thing?
I was kind of interested in writing something for the temple (well, okay, I spent a bored afternoon contemplating giving it a go and half heartedly booting vms and reading code ....)
While I can't answer for the OP, my motivation was specifically that this is kind of an alien environment and the challenge involved in even getting to hello world would definately have seen me walk away at the end the better for the exp, even if walking away from those hours without having gained some marketable understanding of framework foo or language bar.
In the end I didn't do that because the code is insanely complicated (all single letter vars) and my downtime is too precious for such masochism currently; I don't think it's too much of a strech to understand why others might be interested though.
I'm glad to live in a world where such an outstanding personal achievement like Terry's OS really is can exist, and that there are people out there prodding at it.
Isn't it cool that we don't always do things for the money?
I dearly hope that none of the recent templeos projects are attempts to antagonize Terry though. He is a profoundly accomplished software engineer and deserves nothing but respect for his technical achievements from us all alongside understanding of the rest of the package.
(Author here: I cross-posted this comment from a reddit thread, hope it isn't against the rules..)