Sun turns JavaScript into Java. Google turns Java into JavaScript
JavaScript is said to be World's Most Misunderstood Programming Language. Why is the language so misunderstood? It may be the name JavaScript ;). It doesn’t have any relation with Java.
No programming language is perfect. JavaScript has many errors like overloading of +, reserved word policies are too rigid, Semicolon insertion and some more.
When I started working on JavaScript, I felt it an easy language but sooner I was facing many issues like browser compatibility, memory leaks and many other common problems.
There are many sites discussing about all these. I would refer few of them in this post.
Being a scripting language, support of object-oriented programming is quite impressive. Even though there are no classes and instances, there are objects, prototypes, and implicit inheritance.
Browser compatibility issue can be handled using object level detection (Don’t check browsers rather check objects).
Memory leak is a challenging problem. The browsers try to work well with broken web, making it look fine and behave well. This is a very difficult task. If browser fails to collect the garbage that we left, is a buggy browser (memory leak). Most browsers don't do a very good job about memory leak.
I would like to say thanks to Google and many other companies which are writing JavaScript libraries and making JavaScript hot. A good JavaScript Compiler would definitely make JavaScript library implementation easier. Check Google’s web development toolkit.
Mozilla's (Venkman) JavaScript engine has built-in support for debugging, and thus can provide powerful tools for JavaScript developers.
Check following links
if one closure is buggy, then use more closures
http://www.bazon.net/mishoo/articles.epl?art_id=824
Memory Leaks
http://talideon.com/weblog/2005/03/js-memory-leaks.cfm
Javascript library
http://www.thingsthemselves.com/~jeff/computing/jslib/
http://www.howtocreate.co.uk/jslibs/
The Event Object
http://www.webdevelopersjournal.com/articles/jsevents3/jsevents3.html
Obejcts
http://developer.mozilla.org/
Google JavaScript APIs
http://code.google.com/apis.html
DISCLAIMER
This Blog includes links to other sites operated by third parties. These links are provided as a convenience to you and as an additional avenue of access to the information contained therein. I have not reviewed all of the information on other sites and are not responsible for the content of any other sites or any products or services that may be offered through other sites. If you are the owner of any of these links and have any objection please do let me know I’ll remove the link.
No programming language is perfect. JavaScript has many errors like overloading of +, reserved word policies are too rigid, Semicolon insertion and some more.
When I started working on JavaScript, I felt it an easy language but sooner I was facing many issues like browser compatibility, memory leaks and many other common problems.
There are many sites discussing about all these. I would refer few of them in this post.
Being a scripting language, support of object-oriented programming is quite impressive. Even though there are no classes and instances, there are objects, prototypes, and implicit inheritance.
Browser compatibility issue can be handled using object level detection (Don’t check browsers rather check objects).
Memory leak is a challenging problem. The browsers try to work well with broken web, making it look fine and behave well. This is a very difficult task. If browser fails to collect the garbage that we left, is a buggy browser (memory leak). Most browsers don't do a very good job about memory leak.
I would like to say thanks to Google and many other companies which are writing JavaScript libraries and making JavaScript hot. A good JavaScript Compiler would definitely make JavaScript library implementation easier. Check Google’s web development toolkit.
Mozilla's (Venkman) JavaScript engine has built-in support for debugging, and thus can provide powerful tools for JavaScript developers.
Check following links
if one closure is buggy, then use more closures
http://www.bazon.net/mishoo/articles.epl?art_id=824
Memory Leaks
http://talideon.com/weblog/2005/03/js-memory-leaks.cfm
Javascript library
http://www.thingsthemselves.com/~jeff/computing/jslib/
http://www.howtocreate.co.uk/jslibs/
The Event Object
http://www.webdevelopersjournal.com/articles/jsevents3/jsevents3.html
Obejcts
http://developer.mozilla.org/
Google JavaScript APIs
http://code.google.com/apis.html
DISCLAIMER
This Blog includes links to other sites operated by third parties. These links are provided as a convenience to you and as an additional avenue of access to the information contained therein. I have not reviewed all of the information on other sites and are not responsible for the content of any other sites or any products or services that may be offered through other sites. If you are the owner of any of these links and have any objection please do let me know I’ll remove the link.

4 Comments:
Sir kya baat technical blogs??
he he...kabhi kabhi
Nice write up..
May be you have discussed topics in more detail
Thanks,
I just wanted to cover topics which are generally not coved by a JS book. btw I'll try cover these topics in detail in future.
Post a Comment
<< Home