Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve went into argument with my friend, who says that for building applications, using jquery .css function, is more flexible, readable (since attributes sit in the same file), and overall better versus the addClass. For me addClass is much better, since it allows to keep code clean, and keep the logic of functions, outside the style propereties.
What do you think, and if you agree – how can i convince my friend to start using addClass? Or maybe im wrong all along?
In many projects, the fine details of the look, formatting and visual cross browser compatibility of the site are done by a different person than the one who writes the javascript code. Thus, it’s a mess to have the CSS that controls the look of the site intertwined with the javascript of the site all in the same file(s). You have non-JS programmers trying to modify javascript in order to modify the look of the site. This is not a good thing.
However, if you add/remove classes via javascript, then all the actual CSS that corresponds to those classes stays in CSS files where it can be freely worked on without modifying the javascript files. This is a good thing.
Obviously the javascript and CSS are not 100% independent since they often have to do coordinated things, but if they are kept separate, it lets at least 90% of the maintenance be separate rather than 0%.