I agree with a lot of the things Ruskul is saying. Especially this part:
[...] and part of wanting to work with events is that they feel cleaner, more visual, to me, and the moment I can't, it just feels like the core advantage of c3 is no longer present and other environments offer cleaner code spaces.
There is only a single thing that basically everyone in the community can agree on, and that is that the event sheet system is awesome.
My concerns with the whole JS/TS focus lately is that there is no end to it, from now on it will always take a good chunk of resources away from improving the experience of using event sheets. Resources that we are told over and over again are very limited, and I get that, but I disagree with the allocation of those resources.
Entirely new product no one asked for, "Dogfooding" C3 with C&C but actually using Construct more like a framework, or even just as a renderer and doing everything else in JS (though tbf some of the best improvements to old plugin/behaviors actually came from this. But obviously only to the parts that were actually used and not circumvented with JS), C++, JS, now TS, ... where is this going? What is the plan? Is there a plan?
We get multiple new things exposed to the api every single update, but if you want some more ACE exposed for events sheets, from an old plugin or behavior, it's always a year/s long battle.
Another concern, and something that is already happening, is that it's splitting the community, where parts of it now literally speak a different language. It would be something different if it's only people who extend the functionality for all by creating new addons, but it's not. It's split in a way that it's more and more expected to use JS to fix your issue, even though you don't use it yourself.
If you say you don't want to use it you get told to try it, it's not that hard, or something like that. I did try it, but coming from GDScript, it's an awful coding experience in comparison and literally the polar opposite of what makes Construct great and why I use it.