3 ms·
The greatest concern I had wasn't that the update broke a jQuery API, it's that it also broke general JS techniques and IE-specific workarounds that were previo
by Silhouette 17y ago
The greatest concern I had wasn't that the update broke a jQuery API, it's that it also broke general JS techniques and IE-specific workarounds that were previously outside the scope of jQuery.
Also, if even the smallest increments (e.g., 1.3.1 to 1.3.2) can change fundamental behaviour in ways that may require adjustments in existing code to keep things working, then that is a negative point to balance the positive side of using a project under active development. It means you can't count on using any bug fixes or pure performance improvements without having to take on functional changes as well, and that is a significant maintenance risk.