![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
adevyish1. Stars will be playing at the Orpheum on Feb 19th.
2. I am seriously contemplating spending money on getting a webhost. Why.
3. Why the hell are there so many Javascript libraries? Just considering the ones Google thinks are important enough to provide: jQuery + jQuery UI, Prototype + Scriptaculous, YUI, MooTools, and Dojo—that's five. I've been looking at the first two, and I'm still not sure what exactly is in either of them, although Scriptaculous gets points for having a nice summary page with demos of everything.
Honestly, I've been writing my own versions of various core library functions just because (a) I can't figure out which one to use, (b) I don't need the whole library, so really I'm saving on load time (although I do need to start using a code minimalizer), and (c) if I'm careful about how I program, I can beat using an external library speed-wise. That said, I noticed recently that I probably need to build my own JS library, because there are certain functions that I reuse really often. And it was at that point that I started seriously considering using an actual JS library after all.
The real problem is, Javascript is broken. It isn't OO, but you can fake OO (many JS programmers do). There's plenty of deprecated ways to do things that programmers shouldn't use, but use anyway because they're the easy way and guaranteed to be backwards-compatible. Javascript grants too much power to the website (pop-up ads, auto-redirects, etc.). There's a different way to do things for MSIE and not-MSIE, usually because Microsoft came up with a way to do things that the W3C didn't like—and sometimes, both of them suck. This led to people writing Javascript libraries to make up for these deficiencies, which is like wrapping a leaking pipe in duct tape—only works if you're Red Green. Sometimes I think we should just come up with an entirely new paradigm for webpages, rather than old rickety (X)HTML + Javascript + CSS. (Please don't get me wrong about CSS, I adore CSS, but it pales in comparison to LESS which is only in its infancy.)
I have no idea why this post ended up a screed against Javascript, but there you go.
2. I am seriously contemplating spending money on getting a webhost. Why.
3. Why the hell are there so many Javascript libraries? Just considering the ones Google thinks are important enough to provide: jQuery + jQuery UI, Prototype + Scriptaculous, YUI, MooTools, and Dojo—that's five. I've been looking at the first two, and I'm still not sure what exactly is in either of them, although Scriptaculous gets points for having a nice summary page with demos of everything.
Honestly, I've been writing my own versions of various core library functions just because (a) I can't figure out which one to use, (b) I don't need the whole library, so really I'm saving on load time (although I do need to start using a code minimalizer), and (c) if I'm careful about how I program, I can beat using an external library speed-wise. That said, I noticed recently that I probably need to build my own JS library, because there are certain functions that I reuse really often. And it was at that point that I started seriously considering using an actual JS library after all.
The real problem is, Javascript is broken. It isn't OO, but you can fake OO (many JS programmers do). There's plenty of deprecated ways to do things that programmers shouldn't use, but use anyway because they're the easy way and guaranteed to be backwards-compatible. Javascript grants too much power to the website (pop-up ads, auto-redirects, etc.). There's a different way to do things for MSIE and not-MSIE, usually because Microsoft came up with a way to do things that the W3C didn't like—and sometimes, both of them suck. This led to people writing Javascript libraries to make up for these deficiencies, which is like wrapping a leaking pipe in duct tape—only works if you're Red Green. Sometimes I think we should just come up with an entirely new paradigm for webpages, rather than old rickety (X)HTML + Javascript + CSS. (Please don't get me wrong about CSS, I adore CSS, but it pales in comparison to LESS which is only in its infancy.)
I have no idea why this post ended up a screed against Javascript, but there you go.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2009-11-23 03:38 am (UTC)Why the heck do you think there are so many website vulnerabilities.
no subject
Date: 2009-11-23 04:32 am (UTC)