I think the subtext there was that you might have said:
It was just so inefficient to do anything in text adventures compared to what I could do in dungeon crawlers(?), that it almost hurt to type in the commands.
…unless I misunderstood.
For the record, I mostly agree with your feelings on Inform, but maybe not for the same reasons. I’m skeptical about English language programming for most tasks. Maybe it’s good for young students with no programming experience, but then again maybe it’s like how we all learned BASIC on C64 back in the day, because it was easy, and subsequently needed to un-learn all those habits.
I guess this sounds hypocritical coming from someone working on a sort of natural language-like programming language, but in the case of IF, natural language does somehow seem appropriate.
The thing about Inform, to me, is it kinda feels shoehorned. You still need to learn special constructions and do most of the things you’d do in any other language, and I feel like that might be more clearly represented in a standard-issue language. No offense to any Inform fans, it is pretty amazing that it works, but somehow doesn’t feel “natural.”
I’ve tried to go in a different direction here, where “the words don’t matter” and there is less than a handful of constructions. Sentences are basically pure data, and the whole thing can be thought of as a triplestore, with the words on the ends representing two “nodes” with some kind of relationship, and the word in the middle being an “edge” representing the kind of relationship… except that it is actually a tuplestore, so each datapoint is more flexible and can represent whatever you want (weighted edges, multiple relationships at once, etc.)
To give an example from another recent post here, in Inform:
After going south from sandy beach when the red crab is not carried by the player:
move the red crab to shallows.
This is sorta magical-feeling to me; we need to know about how Inform breaks down the sentence in our “query.” In the thing I’m working on, you might write something like this:
player wants to move south, player is in beach? crab is in beach?
player tries to move south.
crab wants to move north.
The difference here being, each part of the “query” directly reflects an existing datapoint, and each part of the result directly represents a datapoint that’s checked for by some engine-level query. There’s no guessing or prior knowledge required about how a compound sentence is interpreted.