This whole idea of extending XForms, as good as it sounds, still has many flaws:
Much of the project relies heavily on a specific implementation of XForms, XSLTForms 1.7, which is why it will not work with other frameworks (like Orbeon).
The same principle may or may not be applicable to other implementations. Even if it is, it will need a complete rewrite of the JavaScript code.
The idea of Extended XForms is to fill the gap between current XForms and the rest of the web, meaning that getting a new version of XForms will heavily affect the project. Most of the code will need to be rewritten, some completely scrapped, and when XForms 2.0 gets to the point that this project is no longer needed, it can be put away for good.
Although this project helps developers write less code, the final XForms code is still large and complex, and unfortunately we can do little to improve its performance when it starts to decline.
Extended XForms syntax is very opinionated; it may look good to some, but for others, it may seem like an extra step rather than a shortcut.
The current implementation uses many CSS and JavaScript files, and although small, they add a bit of a burden on the page's first load. Not to mention that the implementation includes even code that might not be needed in the form being rendered.