Published: Feb 3, 2016 by C.S. Rhymes
Issues with jQuery
When a user visits your site they have to download your webpage and your scripts,but also another library, before they can use your page as you want them to. You could try and improve page loading time through the jQuery CDN, but I recently read an article that gave examples of where sites failed to render at all due to jQuery CDN being blocked. This is a rare example, but it can happen.
I’m not the best person to be giving this advice, mainly because I am lazy. This site uses foundation 5 as its front end which utilises jQuery. So what am I going to do about it? Probably nothing, but one day I might surprise you and write everything from scratch.
It sounds liberating coding everything yourself and not relying on libraries, but then you are missing out on support from the community. JQuery is regularly updated and implements new browser technologies. If you want a new feature then you can update jQuery and migrate your code.
So what should you do?
Well, I don’t think there is a definitive answer that applies to all projects. I think you need to consider what you use at the design phase of a project.
I’m as guilty as most at rushing into coding once the look and feel design has been confirmed, without considering what technology is best for that project.
The other consideration is skills in the team. Will it take too long to skill up your team in a new technology to meet the deadline? But if you don’t do it for the current project, will you ever make time to learn it?