I was certainly broadly aware of the capabilities of TADS. This is timely for me in that I’m starting up a series of classes where our intent was to use Inform 7 but we keep running into issues. Nothing catastrophic, of course, but it’s usually with extensions not working or code examples not doing quite what they say should in the manual.
But one thing that I really do like with Inform 7 is my ability to do what I describe in this thread: Using Quixe in Web Page; Changing Font Size of Display. Not the font size bit so much but specifically the focus of putting a nice, easy to execute interpreter smack in the middle of the page. The page itself can have multiple such interpreter windows, just pointing to a different gblorb file.
Creating exploratory lesson plans for a class is invaluable when you have such an easy approach. I don’t know if that’s possible with TADS. I do know the Online sitegen service was announced but haven’t looked yet to see if that makes things workable like I talk about in that linked post.
The other challenge – and I’ve seen it mentioned a few times above – is that one of the selling points of TADS for me was always the use of HTML and CSS, which are already technologies many people are exposed to and utilize. It always just made sense to me to leverage those. (That’s what I’m doing in that above thread, for example; changing the styles in glkote.css
.) But if online interpreters in particular don’t support those features for TADS, then the fact that they exist in a useful way in TADS becomes much less of a selling point.
I should also note I’ve only explored Vorple a very little bit at this point but if that works as it seems to, and combined with what I showed above in my linked post, I feel like as an author – whether of lesson plan style content or perhaps even a story experience – I have more control over the actual interface and presentation, which thus continues my lean towards Inform.
I could be wrong on that, actually. But it is my perception.
It’s also a bit undeniable for me that getting Inform 7 set up and “just working” is quite a bit easier. For the TADS 3 class I was experimenting with, I had to create the GitHub - jeffnyman/tads3-playground: Simplified Distribution of the TADS 3 Interactive Fiction System so that I could provide an easier means for people to get started. (We use the VSCode extension in that context.)
None of this was likely relevant to this thread. I guess I bring it up just to reinforce what I’ve seen some say: I’m broadly aware of TADS and its capabilities but I’ve always felt the momentum and experimentation was more in place with the Inform ecosystem making it seem like the safer bet.
That “safer bet” perception on my part is even the case with the flux Inform is often in, being under active development (hence some of the issues I mentioned at the start), which contrasts with TADS being in less flux as a general rule.