Or do you think the emergence of asynchronous technologies such as AJAX will reinvigorate the demand for client side scripting and thus require more robust code, which is perhaps available through OO hierarchies and prototypes?
Originally posted by jim cato: Or do you think the emergence of asynchronous technologies such as AJAX will reinvigorate the demand for client side scripting ...
Just look at the emergence of client-side toolkits, and the vast number of books being written on the subject, as evidence.
As Bear Bibeault said, the client technologies are back, we're seeing movement to "fat client" approaches where a lot of processing is happening in the browser, resulting in fewer and smaller server roundtrips and hence, more responsive applications. The plethora of framworks and libraries are one proof, job listings are another, important one if you ask me I know my employer (Yahoo!) is constantly looking for talented front-end people. So yeah, btw, anyone interested in a FE position, feel free to PM me.
Interesting thing is that all objects created with a specific constructor will "see" the stuff you add to the prototype live, even after they are created. This allows you to extend the language's built in constructors.
For example you can add a new method to all arrays.
You can also easily add functionality to any object ever created in your program:
This gives you a lot of power, so naturally it's a little dangerous. Some people like this so much, they even named whole libraries after it
At the end, every object has a link to its prototype, that is the prototype property of the constructor function used to create the object. In Firefox and other browsers (not IE), you actually have access to the link as a normal property called __proto__. So for example:
Joined: Jul 15, 2008
Thanks for your input: very interesting. Good luck with the book.