This is such an open question that it would be impossible to answer correctly. What for? Because the reasoning for such a switch depends on many different factors on technical characteristics, such as jQuery UI widgets, which are used throughout the application, to how convenient you are as a developer with new frameworks. Therefore, in response to several questions to ask yourself to help you decide.
- Am I using jQuery UI widgets throughout the application?
If so, consider introducing solutions to fill in the voids in the JQUI CSS framework. The most noticeable mesh scaffold. Switching JQUI widgets to other providers can be time consuming.
Gridpak sensitive grid generator
Set up Twitter bootloader to fill in JQUI spaces
- Switching to another CSS structure will really help me?
Unfortunately, with well-known gaps in the JQUI CSS structure, the answer to this question (for me) was yes. Mostly I use either Twitter Bootstrap or Foundation, but I still use JQUI, they are just sure about the JS and CSS that I need when I set up the JQUI build.
CSS Framework Basis
- How long will it cost me to switch and then re-factor?
The answer to this question is very important. If you lose a short term from the switch, it would probably be better to continue what you have, however, if the long-term gain is significantly higher than the short-term loss, it can tip the balance in favor of switching.
If you switched, and you haven't done it yet, maybe introducing parsing like SASS or LESS into the equation might be worth it. (SASS is my preferred route)
Twitter Bootstrap SASS'ified
Also check out Compass
- When I finish, have I really achieved what I originally planned?
This is solely subject to due diligence and fact. Know what you are now tuned to before making a decision. This, in essence, is what this issue boils down to.