Comments on: Javascript variable scope, private protected and public http://www.anzaan.com/2009/05/javascript-variable-scope-private-protected-and-public/ Fri, 29 May 2009 02:59:32 -0700 http://wordpress.org/?v=2.8.6 hourly 1 By: admin http://www.anzaan.com/2009/05/javascript-variable-scope-private-protected-and-public/comment-page-1/#comment-3 admin Fri, 29 May 2009 02:59:32 +0000 http://www.anzaan.com/?p=77#comment-3 Its good to have a library handy to take care of simple things like creating classes. It sure makes life little easier. But I think its better to do simple things on your own for the sole reason of making one's code less dependent on third party libraries. And also to ensure another person looking at or working with the code won't require to learn a framework to be able to understand, modify, extend your code in future. I use YUI library pretty heavily these days. I'm stuck with YUI because I'm a big sucker for their dataTable widget and I build a CRUD framework around it 1-2 years back. I'm stuck with YUI on that but I'm quite happy because their libraries are very modular and well-tested and well documented. But at the moment, I'm trying to rewrite all javascript libraries I developed at home and at work so that I can be less dependent on third party libraries. At least to an extend where library code and function calls don't creep into the business logic parts of the code. and I can abstract them away into my own objects so that calls to those library functions are indirect which will allow me to switch third-party libraries in future without having to rewrite everything. I did use prototype initially when I was learning javascript and at that time I thought it was the coolest thing to ever happen to javascript, I still believe it is, but I happen to move to YUI for other reasons. Its good to have a library handy to take care of simple things like creating classes.
It sure makes life little easier.
But I think its better to do simple things on your own for the sole reason of making one’s code less dependent on third party libraries.
And also to ensure another person looking at or working with the code won’t require to learn a framework to be able to understand, modify, extend your code in future.

I use YUI library pretty heavily these days. I’m stuck with YUI because I’m a big sucker for their dataTable widget and I build a CRUD framework around it 1-2 years back. I’m stuck with YUI on that but I’m quite happy because their libraries are very modular and well-tested and well documented.

But at the moment, I’m trying to rewrite all javascript libraries I developed at home and at work so that I can be less dependent on third party libraries.
At least to an extend where library code and function calls don’t creep into the business logic parts of the code. and I can abstract them away into my own objects so that calls to those library functions are indirect which will allow me to switch third-party libraries in future without having to rewrite everything.

I did use prototype initially when I was learning javascript and at that time I thought it was the coolest thing to ever happen to javascript, I still believe it is, but I happen to move to YUI for other reasons.

]]> By: Prajwal Tuladhar http://www.anzaan.com/2009/05/javascript-variable-scope-private-protected-and-public/comment-page-1/#comment-2 Prajwal Tuladhar Fri, 29 May 2009 01:42:01 +0000 http://www.anzaan.com/?p=77#comment-2 Nice post! But whenever I have to create class in JS I use Prototype API http://www.prototypejs.org/api/class/create (I am a bit lazy ;) ) Nice post!
But whenever I have to create class in JS I use Prototype API http://www.prototypejs.org/api/class/create (I am a bit lazy ;) )

]]>