In many ways, we are now in a golden age in this regard, and you will find
almost more options than you might want! So use those libraries, lest you wind up like Tor!
One thing that most of these modern-day libraries, at least the more well-known ones,
have in common is that their quality is light-years beyond what used to be available. More
importantly to you, each and every one of them will likely make your life (in terms of writing
code anyway) considerably easier. There??™s usually no sense in reinventing the wheel after all.
If you are doing Ajax, unless you need absolute control over every detail of things, I can??™t think
of a good reason not to use a library for it. If you know your UI design requires some more
advanced widgets that the browser doesn??™t natively provide, these libraries can absolutely be
worth their weight in gold.
At the end of the day, though, keep in mind that ???naked??? Ajax, as seen in the example
from this chapter, is also extremely common and has many of its own benefits, some of which
are control over what is going on at the most fundamental level and more opportunity to tune
for performance and overall robustness. It is also never a bad idea to know exactly what is
going on in your own applications! If you are comfortable with JavaScript and client-side
development in general, you may never need or want to touch any of these toolkits (I personally
lean that way), but if you are just coming to the client-side party, these libraries can
indeed make your life a lot easier.
Pages:
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105