Quick question:
Does the team developing the framework have any plans on replacing knockout.js with something else?
Apparently 5.x still uses it. If abandoning it is considered, is there a roadmap / calendar about this?
Quick question:
Does the team developing the framework have any plans on replacing knockout.js with something else?
Apparently 5.x still uses it. If abandoning it is considered, is there a roadmap / calendar about this?
It’s more like a dormant idea at this point. We now have “fixed” the main issues we had with knockout (or rather worked around them), so it’s not a priority. Definitely not for version 5. The main ways to avoid knockout issues in specific situations is using dotvvm.state (setState, …) and JsComponent. If you have some specific need where knockout is getting in the way, let us know, maybe there already exists a reasonably easy solution
I believe that the lag from this issue I face: [bp:MultiSelect] flooding the client-side console with warnings & errors + lag
is due to knockout getting in the way.
What do you think?