thissitesucks

8 ms·

1.
by thissitesucks 15y ago
> you're kidding me right? Obviously you filter your queries to the closest node. You again. Smart-ass doesn't suit you. Obviously, you can use standard DOM methods (e.g. gEBTN, gEBCN) with the "closest node" as well. And, assuming you
2.
by thissitesucks 15y ago
> If your decision not to use jQuery (or another lib that makes your life easier) is because of performance then you're optimising much too early. LOL. That's the stupidest thing I ever heard. This is John Resig, isn't it? :) > Pers
3.
by thissitesucks 15y ago
Change your goal to something other than "learning how to program around all of the browser quirks". Why would you need to do such a thing? And if you "enjoy" jQuery, you have no frame of reference. It's far more inconsistent than the DOM i
4.
by thissitesucks 15y ago
That's completely contrary to what I've experienced. Only browsers that "need" a little extra JS/CSS are the old IE versions. Quotes indicate you don't necessarily need to enhance pages in those browsers at all these days. If your experienc
5.
by thissitesucks 15y ago
Nooo... you don't. You are one of those guys that figures anything popular must be smart. Good luck with that . :)
6.
by thissitesucks 15y ago
> But if you absolutely have to support IE6, then yeah, use JQuery. Absolutely NOT. The results vary per jQuery version as they have been struggling to grasp the subtle differences for six years.
7.
by thissitesucks 15y ago
> Why not just use a extremely well tested library that automatically gives you full browser support? LOL. Which library would that be?
8.
by thissitesucks 15y ago
> Having css3 query support in legacy browsers is awesome. No it isn't as you send all of the supporting junk code to the newer browsers that don't need it. > Not to mention productivity gains from method chaining and batch assignme