Tutsplus - Next Generation JavaScript with AMD and RequireJS
Tutsplus - Next Generation JavaScript with AMD and RequireJS
English | .MOV | aac, 44100 Hz, stereo | h264, yuv420p, 1280x800, 30.00 fps | 130MB
Genre: E-learning
English | .MOV | aac, 44100 Hz, stereo | h264, yuv420p, 1280x800, 30.00 fps | 130MB
Genre: E-learning
There are a couple of issues with this method.
Firstly, it's just plain inconvenient. All the JavaScript in all the scripts is loaded into the global “namespace.” Of course, this may be misleading to beginners, who could easily—and excusable—think that identically-named variables in different files won't conflict. But more than that, it's a pain for experienced JavaScript developers with perhaps dozens of JavaScript files. Some files will depend on others, which may depend on others, etc. And you're on playground duty: you've got to make sure they all arrive in the right order, and that nobody clobbers anybody. This can be both tricky or time-consuming, depending on the project.
Secondly—and more importantly—when a browser is downloading and executing JavaScript files, that's all it's doing; it's blocking the downloading of other content until that's done. This is why you've heard it recommended to put your <script> tags at the end of your <body>, instead of in your <head> as used to be the idea: that way, all your other content (HTML, CSS, images, etc.) will be visible to the user before the JavaScript is downloaded and executed. By using one of the many script loaders available, you'll be able optimize this process at much as possible. RequireJS is one of those loaders, and you'll get all the benefits of using it with AMD. For more on this, read the first chapter (and of course all the rest!) of High Performance JavaScript by Nicolas C. Zakas.
HomePage
Screenshot:
(Click to enlarge)
(Click to enlarge)
Tutsplus - Next Generation JavaScript with AMD and RequireJS
