The jealousness is great in this NG, so I am afraid it will just
another vanity fair with "what dork would do like that / what idiot
would code like this??!". I distinctly remember back in 2005-2006,
when the 2nd Browser Wars started, this NG was nearly attacked with
asks to suggests any good library, "please, please, please". The
locals could use it to push *any* programming pattern they like,
literally, so now would be getting the harvest back. Instead the
energy was spend to call sh*t on anyone not willing to write the code
from the scratch. Eventually such demands stopped, people left: for
Prototype.js, MooTools, Dojo etc. And what else was it expected? No
help from clj - no help from anywhere?
For a core library covering coding/DOM trivia the train is pretty much
gone.
Has left the station? You know, it's odd; all of the "majors" have
botched basic attribute manipulation. That's hardly trivia. After
all, DOM stands for Document Object Model. And what are documents
made of? At the "atomic" level? That's right. The train crashed
right after it left.
http://www.cinsoft.net/attributes.html
It is hard but very important to understand.
And apparently none of the authors of the "major" libraries understand
it at all.
No one gives a damn
how perfect, universal, robust, everlasting a commercial use library
is by design.
That makes no sense at all. The code is transparent and often
obvious. When I see code like:-
function removeAttr(el, name) {
el.removeAttribute(el, name);
}
....as is found in Dojo and jQuery. Well, actually; IIRC, jQuery adds
a mystical incantation to try to compensate for a "mysterious" problem
they have yet to understand (a problem that is well over ten years
old).
function removeAttr(el, name) {
el[name] = '';
el.removeAttribute(el, name);
}
Similarly botched renditions of hasAttribute, setAttribute and (most
importantly for the query engines) getAttribute can be found in:-
- jQuery
- Prototype
- Dojo
- Goog (Closure)
- Qooxdoo
- YUI
- Cappuccino
- etc., etc.
What a spectacular train wreck. And for the last few years, those who
read this group have had these lessons drilled into them (whether they
liked it or not). What possible excuse do the authors of the above
efforts have at this point?
The only important things are: how long is it on the
market (2years min),
What?! The longer it has been on the market, presuming it is as
botched as the above libraries and frameworks, the less capable the
authors (at research, reading for comprehension, problem solving,
etc.). Think about it.
how many listed bugs fixed (lesser that 100 means
that at least 20-50 really nasty ones will have to be fixed with your
business loss), how good the support is.
And we know full well about the "support" provided by the "major"
efforts.
And the last but not least nobody really cares what library is bad and
why.
Then can I presume nobody cares what library is good and why? I guess
nobody cares about anything on your planet.
People normally want to know what library is the most usable /
the best and why.
And what does "best" imply?
If the consensus still is that there is not such
library and the only sane option is to write your own from the scratch
You are the only person here who keeps parroting that "from scratch"
line year after year. It's famously *not* something that is
recommended here. Just as you are famous in your way.
then it is better to stop the discussion right here so not making
another fun out of yourselves.
There's no need to make fun of you Veek. Your posts are funny enough
in their own right. And I see you as a tragic figure, dug so deep in
a hole of blunders and misstatements that you have no shot at ever
seeing the light of day again. Give it up.