After a major release interlocutor (1.6.x) the jQuery team starts with a substantial refactoring of the code with the new version 1.7.
This is a version that adds many new features, introducing significant new features and above all starting to discourage users from 'use of other despicable.
All this effort in preparation for the 1.8 that is not backward-compatible announces, what to say while you learn the best practices with the new 1.7 from 1.8 because many commonly used functions that we have identified as being of little use, or because of confusion will be eliminated.
The intention is very clear in the article posted on the official blog titled "Building a Slimmer jQuery" which you can read here
The team starts with a questionable assumption: the jQuery version 1.2 now has expanded a lot, at the level of wealth of functionality as well as in terms of size. If the first aspect we can not complain, in fact, for the second we went from a 79K to a framework of 250k. It's no good. If the problem is for fast connections, it becomes an obstacle quanso of mobile applications. And the team has realized, like all the other hand, that much of the future is right on that technology.
To give you an idea I created a graph with LibreOffice:

Completed the introduction of a duty to pass new starting right from the deprecations in detail:
| |
CSS Course
Web Design and Accessibility according to W3C CSS and XHTML. Starting from 29 €. |
| |
HTML Course
The markup language for the Web from 29 €. |
| |
Javascript Course
Complete guide to client-side scripting. Starting from 39 €. |