Management decision was to release TCC-RT.
There's no reason to even look into TCC/LE anymore.
TCC-RT doesn't have a command line. They're different products with different goals. The main purpose of LE is give a
taste--but then you have to
buy the
carton of ice cream.
The reason for TCC-RT was a lot of companies would see TCC and think, "Hey, that could be pretty good! ... But we're not going to spend tens of thousands of dollars so we can put a copy on every virtual machine on our server farm." Better to get a few sales of the development tool and give away a run-time than get no sales. And, of course, developers would recommend it to their friends--but only if their employer bought copies of TCMD in the first place.
It's not an either-or situation.
Realistically, I can't see anyone looking through the App Store and thinking "Wow! A free super-pumped-up CMD without a command line or any kind of debugger! Let me get that! Hey--maybe they have other stuff!"
With TCC/LE it'll be like the company I work for--"Let's try the free version first." I did original
development work with my personal TCMD copy--but I couldn't use UDF's or array variables because LE doesn't support those. Then it got to, "You know, we
really need the
paid version if we're running it on another PC." ... "Okay, we'll get it."
(By the way just so we're clear--I'm
not a programmer, I'm a lawyer; my boss has been told by every consultant she has spoken with that she needs a full-time in-house IT person, but "it's not gonna happen" and I'm the one who gets stuck with it. So we don't have commercial development tools like Visual Studio, etc.)