I very much enjoy the standard TADS 3 Windows IDE. The syntax highlighting and auto indentation provide a lot of feedback on errors (mostly punctuation) during the writing process and save me a lot of time.
For Inform 6, I prefer VScode. Its built in terminal window is perfect for testing while writing and it works well on my RPi. Inform 7’s IDE is incredible. I just prefer TADS and I6. BTW, the new version of I7 works well on the RPi too!
This might be an unpopular opinion around here, but don’t see the appeal of the Workbench at all. The UI really shows its age and the ide doesn’t do much a normal text editor + terminal window can’t. Plus, workbench tends to clutter your makefile unnecessarily.
I can solve 98% of errors without a debugger in less than 10 seconds, usually. Though I apparently have this weird curse that causes debuggers to go missing, so I’ve had to learn—out of necessity—to do without.
However, with that said, would I appreciate having a working debugger in TADS 3? Absolutely.
I’d probably use the debugger more if it was standalone/usable from the command line. But in practice the only thing it does that really seems useful is the ability to set breakpoints and step through execution, and so I end up faking them with my own roll-your-own debugging methods.
If T3 had a debugger like gdb and a memory profiler like valgrind that would be very cool, but I’m probably one of like 1% of the already tiny T3 user base that cares about that kind of thing.