I was working on a simple landing page for one of our projects and suddenly my boss, who happens to be a CTO, tells me not to use jQuery. He thinks it will be embarrassing when other developers discover we still use jQuery in 2019.
In my opinion, it's completely OK to use jQuery in simple websites rather than converting each project to React or Vue powered. Do you agree with this?
From the perspective of a CTO, here is what I'll think
- It's a landing page, everyone will see it. If someone looking for a job and find that this company is not using modern technologies, some may not consider it
- We're teaching new dev React, not JQuery. So if there are any edits, even juniors can do it
- Performance wise both React and JQuery are really good. But by default React comes with great tooling (CRA). Like Eslint, Sass support, enforce component splitting, etc
- Use familiar plugins/libs if need in future. Suppose your CTO, as well as others, who are already familiar with React libraries (than JQuery) it will be much easy to integrate
- Longer vision - For now it may seem like a simple landing page. But if future it may evolve into something large
There are many more if you think from the perspective of a CTO. Please don't blame him.
Hashnode is a friendly and inclusive dev community.
Come jump on the bandwagon!
💬 Ask programming questions without being judged
🧠 Stay in the loop and grow your knowledge
🍕 More than 500K developers share programming wisdom here
❤️ Support the growing dev community!
I might be embarrassed to use jQuery for a *simple landing page." Not because jQuery is dated, or I give a hoot about others' opinions, but 'cuz it's big...is the weight of jQuery justified? VanillaJS remains a viable option.
If the use of jQuery is reasonable, is it adequate? If it is reasonable AND adequate, is the landing page the front door to a site/app/platform that will use other, more heavy-weight libraries? Once you and your visitors pay the download cost for your choice of library the first time, it likely won't need to be paid again; if jQuery won't be used for the remainder of the app, then I would probably standardize the landing page to use the heavier-weight kit that will be common throughout the later parts.
Does your shop own a population of developers similarly well familiar with jQuery and your other library(ies) of choice, e.g., those favored by your CTO?
There's a network of interrelated issues to drive the decision as to which, if any, framework(s) to employ. I'm mostly concerned with performance, user experience, supportability, and cost-over-lifetime. I see the balancing of concerns such as bandwidth, shop standards, and developer skills as the measure by which to assess jQuery's appropriateness for use. The opinions of "other developers" as relates to the age of jQuery (or any tool extensively represented in my code-base) strike me as irrelevant.
Hammers come in different shapes and sizes for a reason. A hammer's age should rarely be the basis for choosing it.
jQuery is a tool, and as long as you have a proper use-case (like supporting old browsers), it is ok to use imho!
Just make sure that you know about the current vanilla JS API, because many things jQuery was useful for were standardized and are now available directly in browsers (like
querySelector() and the Fetch API).
No; I do not agree.
In my opinion, it's completely fine to use jQuery; not embarrassing at all.
It is the same as saying "why are you driving Toyota Prius (as an example) when there is Tesla (for an example) or maybe Ferrari"
Every project has needs and it is useless to overengineer projects just for the sake of doing it.
If I don't need to use React; I won't; I might get the things to get done with jQuery.
If I don't need to use jQuery; I won't; I might get it done with vanilla JS 😎.
P.S. In fact, I write about the tutorials without Framework in mind but the problem in Mind. Check them out at time2hack.com