New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plan of support for knockout.js #2602
Comments
At time of writing:
So I would say its support has already expired. Taking a cursory look at issues will make apparent to anyone that there are a lot of inconsistencies and serious performance flaws.
|
Thanks @webketje for the thoughtful response. I agree updating the readme.md would be wise as well as marking the package feeds as deprecated for tech audit. Most teams have been using knockout for observables. For now, I will be guiding teams away from using knockout.js in all new features with a strong recommendation towards replacing knockout entirely. |
My team has been through the same process of evaluating the future of knockout as a library in our projects. We never had any technical issues with the library itself. Productivity is always great due to the elegant design of knockout. However, due to the age of the library, we did our due diligence to find a replacement. I would like to mention solidjs as one of the better alternatives to knockout. According to @ryansolid Ryan Carniato - the author of solidjs on this article
solidjs rank consistently on top on majority of the benchmarks. Thanks! |
It looks as though they're steering people to TKO as a replacement: https://github.com/knockout/tko |
This is more of a tech-audit issue than a functional issue: What sort of timeline do the contributors to knockout.js expect to support it?
I ask because the issues are not readily adjudicated and we are a few months away from the 10 year anniversary of an issue of an unsupported dependency: #788
The text was updated successfully, but these errors were encountered: