In all your three examples, the product they create is detached from the creation platform before release, and that product (text, music, images) is compiled/played/displayed on a different application; an also there are many alternative tools where the product could be processed if the original tool ceased to exist.
So there's no fear with those that, if the tool creator begins imposing more and more restrictions, you'll be locked-in. But a unique programming language for which your code can't possibly be ported to a competing platform? One would be stupid to develop for it anything requiring ongoing commercial support, beyond some cool tech demos.
Anyway not here looking to start a flame war. My point was that the product can be good or bad and it doesn't have anything to do with it's source code being available or not.
My 5c. Everyone feel free to disagree.
A product can be good or bad without OS. So long as you can deploy what you make with it effectively.
Sometimes that means mindshare, like UDK and Source.
Sometimes that means complete decoupling tooling from code like Sublime and Atom.
Sometimes it is more about the deployment, like Visual Studio and Unity.
However, to stand out, this product needs one of the above.
It's new, and doesn't seem to be backed by a big name, so no mindshare yet.
So they need to somehow make devs want to use it for their code. A nice experience is usually not enough.
An OS community, or a fantastic cross-compilation strategy are the only two things that I, personally, have seen work.
OS seems to be the easiest of the two.
While I side with your central argument, there are numerous cases where the above is absolutely enough.
There might be a cost/benefit analysis where some closed platform is extremely far ahead in every other aspect, but you should be very well aware of the risks of being tied to that platform.