How come the answer to every javascript question ends up being "jQuery" -


I've been following JavaScript questions for the last few weeks, and I've got a common recurring topic. / P>

Almost any question has been asked here in which JavaScript is included:

  1. "jQuery can do this"
  2. "There is a plugin for this" / li>
  3. "jQuery can make your bed for you."

Even the questions that refer to other libraries are answered by saying "Use jQuery instead".

Is jQuery completely replacing javascript?
This is a serious question. Are we really looking at the JavaScript future? Obviously this community has a strong bias towards jQuery (is it because there is a lot of .NET developers?), But is this a prerequisite to fully share the web development community?

I think jQuery can not replace javascript for a very obvious reason. This is because jQuery does not solve any single problem, it only resolves problems with an incompatible implementation between the browser, which is its biggest strength and it comes with some syntax Chinese.

jQuery can not change the DOM API for another obvious reason: JQuery - Library is controlled by an organization, and primarily on the other hand, DOM is a specific spec by many vendors While jQuery has been implemented, jQuery only has a cover around the various implementations of that sample.

If jQuery wants to change these, then this is a spec, because different browser vendors can not be just applying their code and throwing it in elsewhere and everything is working well. The browser engine can be in C, C ++, Java, or GolfScript, so it becomes absolutely necessary for a specific imagination instead of implementation.

Once the jQuery API becomes D-Facto standard and takes it out in a fantasy, it will face the same problem that now faces eyeglasses. You can not be just a core-comet who resolves a problem overnight and releases a new version, which says that 1.4.3 is of space. Imagination has been considered, agreed, modified, released, and all the implementers will have to update to update their codebase which makes the whole process slow. It also loses the ability to fix cross-browser quits because it is not in control because it is operated at a higher level in its Chair.

Again, because it is a fantasy and is moving slowly, you can always come up with your own library * Question , which simplifies the next API , Fixes cross-browser issues, and moves at very fast speed.

Why this can not replace the jQuery DOM API, because if this happens, then it will remain better, more innovative, and compete in reflected every single day. .


Comments

Popular posts from this blog

paypal - How to know the URL referrer in PHP? -

oauth - Facebook OAuth2 Logout does not remove fb_ cookie -

wpf - Line breaks and indenting for the XAML of a saved FlowDocument? -