It’s funny you mention adv3Lite, because after a couple hours of research and messing with both yesterday, I had already decided to go with it! It’s really great in my opinion; it feels like it captures all of the best parts of Inform for me — especially regions, instead of rules, relations, scenes, and a design philosophy that favors composition over inheritance while still offering most of the convenience classes provides by adv3 — while also bringing with it the best parts of TADS and adv3.
Honestly, I was worried that I would miss a lot of features going from Inform to TADS and thus, no matter which one I chose, I’d end up being unhappy with my choice. But thanks to Eric Eve, I’m actually completely satisfied! I feel like I have a library that does everything I could possibly want it to do.
In fact, it has so many amazing and useful features, implemented in composable and coherent ways, that porting over my code from Inform has been a blast — it often takes three seconds to do something that took me 30 minutes in Inform. Not just thanks to the standard library but also thanks to TADS. It’s a really well designed language that’s easy to use, succinct, and flexible. It feels like programming in Ruby a bit actually, which is a very high complement in my opinion because — while it isn’t the best at performance or correctness — it absolutely is the best for just sheer enjoyment and flexibility of prototyping.
To your point on templates, I’ve seen a little bit of what they can do so far and I’m actually incredibly impressed with them. They really add a lot to what makes the language great I think, because they allow you to be even more concise than Inform at its best without sacrificing comprehensible and consistent syntax.
One other thing I really want to compliment TADS for is the documentation. Eric Eve is amazing at writing technical documentation. I’m going through Learning TADS 3 with adv3Lite, and the conciseness of the writing combined with its thoroughness and attention to providing useful examples is a breath of fresh air compared to the Inform documentation — as are the automatically generated standard library docs, the system manual, and the library manual. I was concerned that a big problem with writing in TADS as opposed to inform would be that there are basically no Google search results for TADS, so if I ran into a question about how to do something I’d be at a loss. But for the first time in nearly a decade of programming in various languages, I’ve found that I don’t really need to Google search anything when programing with TADS. Everything just seems to jump out at me when I need it.
Also I don’t miss the Workbench at all. I’m an unrepentant Emacs user and not only that but I’m extremely dependent on VIM key bindings so most pre-made IDEs for things are kind of useless to me. Instead I’ve just been working on improving the existing tags three mode for Emacs. It’s assuredly missing many of the features that the workbench offers but I’m content to use it for now and I’m going to be expanding it over time as I figure out how to do things.
Sorry, I just had to gush.