The main advantages to adding jQuery to your toolbelt would be:
browser compatibility - doing ...
Let's talk about cars.
Oh wait, we already did - remember that time we met, some time ago? We talked about cars. In fact, you seemed to be quite the expert on cars. You were able to explain, in detail, all of what's right, wrong, and exciting about the latest Formula 1 race. You knew by heart all of Lamborghini's models, including their price and ...
To answer that question, I'm going to ask you a rhetorical question about another structure that have similar property to the DOM elements that jQuery manipulates, that is the good old iterator. The question is:
How many operation do you need on a simple iterator?
The question can be answered easily by looking at any Iterator API in a given language. You ...
Start your for loops where ever you have to start them.
It's called write modules, maintain modules, and share modules with the community, build popularity, etc.
There are various conventions for it.
The Level 2 DOM API provides the getElementById, getElementByTagName, and getElementsByName methods. To this day these are ...
Today, in our work as in our life, it is more important know how to find information rather than know the information itself. I mean that a good developer is a person able to find documentation, network, and that share with an open mind.
I am an experienced .NET developer and, believe me, for every project I work on I have to learn new things about the ...
Never expose direct access to your database from the web layer. You can never lock that down; someone will send "DROP TABLE table" to your server, however much you lock down the JS source.
All they have to do is see what the browser sends to your server to detect that your server accepts arbitrary SQL commands.
Not that you can lock down the JS code; it is ...
It's more important to study the language than it is to study the framework. Learn the language well, and you'll use the framework well.
In order of importance (most important first):
Fundamental programming principles - Algorithms, data structures, etc.
Language paradigms - OOP, Functional, etc.
Syntax and frameworks.
You should upgrade with each release of jQuery -- just take a peek at the update logs before updating.
The jQuery team is very good about documenting API changes and deprecated calls. At this point, the vast majority of the API is quite stable and probably won't change. Most changes are behind-the-scenes bug fixes that do not affect the outward API. This ...
Update your version of jQuery if and only if you need some new feature that's included in the new version. Simple as that.
If you frequently develop using jQuery, keep an eye on the official blog to know when updates are released and what they offer. Wait a couple of weeks or so before upgrading to the latest version to make sure any unexpected bugs get ...
There are a lot of complications involved in making a functional board. These include:
Mission and philosophy: jQuery set out to make DOM manipulation easier to use, and had a single minded focus on achieving that goal. Other frameworks like Mootools and Dojo focused on making it easier to create complex applications, an idea that was ahead of its time (in 2007), and split the attention of the community and created unnecessary complexity for ...
There are advantages, but it's debatable whether they really outweigh the drawbacks.
The main one is that you save bandwidth and gain faster responses. jQuery adds another ~30kb to your response. On some networks (and in some countries), that could mean a few more milliseconds. On the other hand, though, you can set up caching for it rather easily using ...
Actually, what you're describing exists already for years. It's called caching. And it's available not only for JQuery, but for everything your browser may download.
Then sites could check "local" first, before CDN, before finally defaulting to downloading from the website server itself.
This is exactly what every browser does. It checks local cache ...
There's no technological reason why they couldn't. However, it's not necessary and it's against the web's fundamental philosophy. It's not necessary, because you can achieve almost the same thing with a far future expires header. It's against the web's philosophy because it causes there to be a top-down, centralized authority on which libraries should/...
First of all, we have to get something straight:
People like being black and white.
If you're going to use a cross browser normalization tool then use it. Don't use it to normalize some things but not others.
var a = $("#foo");
var b = document.getElementById("bar");
Those two should not be mixed. Either you use jQuery for edge case bugs you might care about or you use the DOM for speed, but ...
The problem with "chess program" as a concept is that there are many pieces which can absorb a lot of time, and not necessarily interest you at the moment. You can spend years just working on graphics, or an alpha-beta search, or a visualization to help develop for the search engine, or... well, there are lots of pieces.
I recommend finding an open source ...
Libraries have a payload that eats bandwidth. But as people already have pointed out in the other answers you can limit this with gzipping and caching. If you only want a subset of jQuery you can do with SizzleJS and with ...
I suggest you to read this article which I think explains pretty well why extending objects is a bad idea, with regard to Prototype also.
Lack of specification
Exposure of "prototype objects" is not part of any specification.
[...] In order for implementation to conform to DOM Level 2 fully,
there's no need to expose those global Node, ...
About jQuery. I was programming with DOM APIs since 2001 and can assure you that a simple and well-tested DOM API like jQuery lets you work more on the real problem rather than on the API.
I also manipulated DOM in ...
Reasons I know:
When the need is extremely minimal, say 1 onclick.
When download speed is critical and the jQuery library is too large AND you don't have to write much (custom) code to replace it.
When integrating with other technologies, sometimes raw js is better.
When working on a legacy system (aka 'production') already written in js with established ...
To really give an exact answer to your question: Yes.
Although JQueryMobile is meant for web applications (as pointed out by Yannis Rizos), you can use Phonegap to create native applications with JQuerymobile.
What Phonegap does, is create a native app with a webkit browser embedded. So it still is kind of a web application, but also kind of a native app, ...
Learn the DOM. By doing that, you will have a better understanding and appreciation for what libraries like jQuery do for you. This also means you'll be better suited in the long run if you must change tools. The DOM will always be there, and is common ground for understanding the fundamental design choices for any given library that interacts with the DOM.
Only Test if it Brings Value
I don't test typically, but if I did I certainly wouldn't aim for any percentage number of coverage or loading tests in front of everything I wrote but rather focus on handling of things I don't control and things that were coded poorly that I don't have time to rewrite.
If behavior of things I do control and that I did in ...
Let me rephrase:
You could/should make it harder to use a token. Implementing a max-usage per token, a max life-time, ... It is however impossible to know if it is the scriptkiddie or your 'application' contacting your api.
A lot of people tend to forget that it is never the aplpication calling the api, it's the application, telling ...