> being forced to use JS is not their idea of fun. QML is not JS. Indeed, lots of high-quality QML applications use basically zero JS inside their QML, and hea

> being forced to use JS is not their idea of fun. QML is not JS. Indeed, lots of high-quality QML applications use basically zero JS inside their QML, and heavy JS use is widely (but not universally) considered an anti-pattern. If using QML is forcing you to write meaningful JS (vs you choosing to use JS for whatever reason), you are probably holding it wrong. (sure, technically "property: a + 15" involves JS because "a + 15" is a JS expression, but not in any sense that a C++ programmer would mind)