The Complete jQuery Course

JQUERY is nothing but a JavaScript library that you attach to your front end files in order to enable some additional features or functionality which primarily comes from plain vanilla Javascript. It's just an external file or a JS code that someone has already composed for your ease. Bootstrap too is somewhat similar to an appendage of CSS. Most significantly, it is widely used for its Responsive Page Designing feature that enables your Web page to conveniently accommodate it's dimensions on whichever device it is going to be displayed on.

jQuery Mobile itself "enhances" standard HTML markup along with JQM-specific markup by running its Javascript prior to displaying the page, then their CSS styles the page. By using a lot of JQM-specific markup they add a ton of functionality that is mostly geared for the mobile space (but can also look fine on a desktop browser - e.g. see their docs for good examples).

At first, they look like competitors, but aren't. The main difference is: JavaScript is a programming language, while jQuery is a library. jQuery exists because JavaScript was born first. They serve totally different purposes. JavaScript can live by itself, while jQuery doesn't. JavaScript [1] allows you to make everything from a programming language perspective: functions, loops, data structures and all that it's paradigm involves. For more information, don't let to check the references. jQuery [2]: jQuery is a fast, small, and feature-rich JavaScript library. It makes things like HTML document traversal and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API that works across a multitude of browsers. With a combination of versatility and extensibility, jQuery has changed the way that millions of people write JavaScript. In general, for a basic comprehension, jQuery uses resources given by JavaScript to make things easier while manipulating DOM [3] and a lot of other things (Ajax, JSON, events). This is not simply a comparison. It's like comparing oranges and bananas. I don't know any other programming language to compare with JavaScript - it's a hegemony when we talk about web and browsers. For jQuery, there are a lot of other libraries available. Everything you do with jQuery, can be obtained using JavaScript, but you will have to write much more code. There exist ups and downs that you must evaluate. Some jQuery alternatives are: MooTools Prototype JavaScript framework YUI Library The examples above are merely to illustrate what libraries/frameworks are. It's not the goal to discuss which is better or which is more complete than others. [1] JavaScript [2] jQuery [3] Document Object Model

JavaScript: JavaScript (JS) is a dynamic computer programming language. It is most commonly used as part of web browsers, whose implementations allow client-side scripts to interact with the user, control the browser, communicate asynchronously, and alter the document content that is displayed. It has also become common in server-side programming, game development and the creation of desktop applications.[Wiki] jQuery: jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML. jQuery is free, open source software, licensed under the MIT License. jQuery�s syntax is designed to make it easier to navigate a document, select DOM elements, create animations, handle events, and develop Ajax applications. jQuery also provides capabilities for developers to create plug-ins on top of the JavaScript library. This enables developers to create abstractions for low-level interaction and animation, advanced effects and high-level, theme-able widgets. The modular approach to the jQuery library allows the creation of powerful dynamic web pages and web applications. Used by over 80% of the 10,000 most visited websites, jQuery is the most popular JavaScript library in use today.[Wiki] Javascript Vs Jquery JavaScript has long been the subject of many heated debates about whether it is possible to use it while still adhering to best practices regarding accessibility and standards compliance. The answer to this question is still unresolved, however, the emergence of JavaScript frameworks like jQuery has provided the necessary tools to create beautiful websites without having to worry (as much) about accessibility issues. I�d strongly recommend going for JQuery (or another JavaScript library) instead of raw JavaScript. You can do very complex things with one line of JQuery that would take a lot of coding and debugging if you were to use raw JavaScript. Ultimately you will need an understanding of the underlying language to take full advantage of JQuery but if you want something you can deploy today, start with JQuery rather than JavaScript. Performance jQuery in terms of speed is quite fast for modern browsers on modern computers. So is pure JavaScript. Both run drastically slower on older browsers and machines. Pure Javascript to access the DOM can be faster as you can cut the overhead that jQuery has on this. However it doesn�t always have to be faster as you could write some major mistakes that slow things down again. jQuery on the other hand has been battle tested over the past few years and is proven to be fast and consistent. [Source: jsperf.com] The main advantages to adding jQuery to your toolset would be: Browser compatibility � doing something like .attr() is much easier than the native alternatives, and won�t break across browsers. Simplification of usually complicated operations � if you�d like to see a well written cross browser compatible version of an XHR method, take a look at the source for $.ajax � for this method alone it�s almost worth the overhead of jQ. DOM selection � simple things like binding events & selecting DOM elements can be complicated and differ per-browser. Without a lot of knowledge, they can also be easily written poorly and slow down your page. Access to future features � things like .indexOf and .bind are native javascript, but not yet supported by many browsers. However, using the jQuery versions of these methods will allow you to support them cross browser. To Summarize jQuery like any other good JavaScript frameworks supplies you with functionality independent of browser platform wrapping all the intricacies, which you may not care about or don�t want to care about. I definitely recommend JQuery! It is made up of JavaScript libraries and also easily compatible for all browsers. As per my experience I will be glad to give an opinion about JavaScript /jQuery. I agree that developers should have at least some understanding of JavaScript. jQuery and similar libraries might be a good way to get people interested in JavaScript in general. But in the other hand it might actually be a stumbling block � it�s so easy to use jQuery that many don�t need a deeper understanding of JavaScript. The best thing about jQuery is that it is tailored to be simplified. Also, there are many already pre-made plugins, UIs, and widgets. Another important note is that straight JavaScript can take 10-20 times as much development time, requires more debugging, more knowledge of the language and browser compatibility issues, etc. Yes, straight JavaScript is the best performing method of client-side development, but a library like jQuery will get you to market faster and cheaper, so it�s a better option for a first-run of a product. Custom-code all the script once you�ve established your product and have the revenue to go back and refactor the code. Don�t forget to tell us which technology you use while developing web application. Please leave your comments, feedback and suggestions in the comments section below.

I wouldn't say �outdated�. It still works and it's still relevant. It's just not as useful or necessary as it used to be. jQuery's major strength was that it offered cross-browser compatibility at a time when JavaScript standards weren't uniformly implemented. A few years ago if you wanted to support IE8 then you basically had to use jQuery. It offers some handy functions for animations and AJAX requests but the majority of people used it just for it's selector functions, being able to conveniently and reliably select any element by wrapping it in $(""). Slowly however, other native solutions have become more reliable as browser vendors have implemented the same standards. These days you can get really good browser support without jQuery. It was shown that doing animations with jQuery was very bad for performance, not to mention the overhead of including the library itself. They did make the individual modules available through NPM, allowing developers to require just the bits they needed (e.g. just use jQuery's handy AJAX functions), but today these are now essentially just polyfills for native solutions. If you want to select elements you can use document.querySelector. If you want to modify classes, attributes, data-attributes, you can use element.classList, element.setAttribute, element.getAttribute, element.dataset. If you want AJAX you can use fetch, etc. The industry has a lot to thank jQuery for. It inspired a lot of what is today standard native functionality in browsers and it made JavaScript so easy and accessible that it now stands as one of the most popular and fastest growing programming languages. However, it is no longer strictly required, depending on which legacy browsers you need to support. I don't include it on any projects anymore.

Here are the some books that can help to learn jquery.

 

• Learning from jQuery 1st Edition  (English, Paperback, Callum Macrae)

• Learning jQuery 3 - Fifth Edition Paperback – Import, 29 May 2017

  A Smarter Way to Learn jQuery: Learn it faster. Remember it longer. Kindle Edition

  Learning Jquery, Third Edition  (English, Paperback, Jonathan Chaffer, Karl Swedberg)