Quote:
Originally Posted by Kor
It was only a quick example. It is awfully easy to create a prototype in order to retrieve multiple className as well. No, thanks, I don't need frameworks for that either.
|
Setting aside that the W3C DOM is, itself, just a framework…
Awfully easy? Your flawed example suggests otherwise.
Despite your experience, you failed to remember to account for it, thereby demonstration the frailties of attempting to reinvent the wheel every time, rather than demonstrating the superiority of self-written functions, as had been your intention.
My point is that you should perhaps open your mind to the fact that there are people out there, with vast experience using and developing for js, who appreciate that there can be considerable value in frameworks.
Or do you consider people such as John Resig, Dustin Diaz, Nate Koechley, Doug Crockford and those at the YDN to be lazy, weak developers?
Do you consider the developers behind
these sites to be lazy, weak developers?
If so, what impact do you think it's likely to have had on their output or the effectiveness of the sites in which they've utilised js frameworks?
Of course, having a solid foundation in js can only help (in the event of bug occuring in the framework itself).
I completely agree that frameworks work best in the hands of those who do have a solid, though not necessarily exhaustive, foundation in js.
However, imo, there's absolutely nowt wrong with using a framework shorthand to enable developers of all levels to expedite the development process or to open a project to progressive enhancements from which the project might benefit, but which the budget or time restraints would otherwise rule out.
If you're happy writing your own 'DOM Ready', AJAX requests, class handlers and assorted other functionality every time, go for it. But, that's a personal thing and has little, if anything, to do with supposed limitations of frameworks or those who use them.
Sure, there are going to be a fair amount of framework users using it because they don't know how to do it well using the W3C's own API, but there are significant numbers out there using them because they'd rather get on with the job than waste time trying to impress either themselves or their peers with their js ninja skillz.
Now who's being lazy and weak.
I'd say about as much thought went into that as went into your
getElementsByClassName function.
