The problem with Clojure is that it is being a functional language, which is imho very hard to understand, especially in a world of developers mainly used to object oriented programming, but instead advocates for immutability, which is super important in editors that operate on data all the time. Of course, there are other solutions, most conveniently multi paradigm.
The other problem is the mentioned by @britzl complexity of the graph system of the Defold’s editor.
I have a not so pleasant experience with making an editor for a complex system of data and it’s a hard task to handle on its own. Moving it to other technical platform is not an easy task and it would be a hard decision to make, also from economical point of view as Defold is utilising the current resources to squeeze as much as possible and advance Defold.
On the other hand, technical platform is just a fraction of the problem, though I think really important, because devs are not able to easily create extensions and tools for Editor that are useful in gamedev and it turns out custom tooling is very, very important in gamedev as each game has its own need.
There is no golden rule what is useful, what is important and choosing priority is always somehow arbitrary. One might say camera components needs improvement, while makers of one screen games would be totally neutral to this and would instead demand for example more comfortable GUI features.
What looks more reasonable is approach of not neglecting those single case needs, because that’s what powers the most popular engines, but obviously it’s costly.
I do agree with @Pkeod that Defold have an egg and chicken problem on scaling and somehow is blocked on commercialisation of some Defold ecosystems. This is not also particularly only negative site, because on the other hand it’s also a big plus! Almost everything related is free! But isn’t there a problem of saturation of what’s possible to be done for free, yet people are still demanding more tools and solutions to their problems in gamedev, that they would, if provided, pay for?
So, if we identify the problems, what are the possible solutions?
Community Editor for Defold (or Wefold ) would have by now existed, if there would be enough interest in Defold, I think. I would make myself at least a try at making an Editor for Defold in Qt or maybe PyGUI, or JS or as an PWA (so that’s an online tool/service?), you know, something that is popular (and simple) enough to interest those wanting to improve their skills, make portfolio and contribute.
But it’s also a very hard task and would demand at best a technical leader with huge experience and architectural vision that would be able to maintain it all the time (like mentioned data immutability and general data orientation, ultra fast streamlining and managing of resources and convenient and easy to expand tooling) that is also a good strategist and marketer (this doesn’t have to be one person).
It is by now pretty established that community of Defold is mainly demanding ability to extend Editor tooling to suit their needs and I am pretty sure Defold team is aware of this and is definitely making steps in this direction, not huge leaps as we would ideally wish to have, but small steps.