• posted 2 years ago
    • 5 comments

    jquery vs mootools: my initial thoughts

    mootools_logoI've been using jQuery regularly for my new job now for about 3 weeks or so. I've used the selectors, event handling, short cuts/handlers, animations, plugins etc. Nothing too fancy, but in general, a descent exposure. I'd like to compare it with Mootools. And while I do rock a Mootools skin on my phone, I'm going to try and remain as objective as subjectively possible. I'm going to try and stay positive about the differences and give use-cases for using either.
    read
    • posted 2½ years ago

    Flexibility: Server side vs Client side

    flexibilityI've been told by many people, veterans in their respective industries such as family friends, family members, etc., that when you're in a technical field, the best type of job security is to specialize. I imagine this would extend to a lot of different areas (entertainment, finance, management, etc.) but especially in the technical/programming arena, I find it's very true and productive.
    read
    • posted 2½ years ago

    Jumping the gun: html5/css3 is not here yet!

    Picture 1On Twitter, I follow a bunch of people in the development arena. JavaScript framework core developers, designers, mysql/php architects, etc. etc. I'd say about 50% of the people I follow are in that arena (the other 50% probably being aggregators or tech news sites/blogs).

    A consistent theme I'm finding in the past few months has been css3/html5 posts. They talk about new effects, rules, possibilities, etc. etc. Now I try to be optimistic about web development; I try to practice valid w3c content, semantic markup, everywhere I can. But the age of css3/html5, at least for me, is still so far off. 25% (at the least) of internet users are still using ie6, another 40% are using ie7; that takes us to about 65% of internet users using subpar browsers (ie7 is a step up, but still very much sub-par) that don't support anything close to css3 and html5.
    read
    • posted 2½ years ago

    Client side framework's should be called client side libraries; here's why:

    library-booksThis isn't a really important post, it's just something I think need's to be expressed and accepted; it must be accepted. Mootools, YUI, jQuery, Dojo etc. are great. They help a person with very tedious javascript techniques, speed up your applications, and make the UX much richer.

    But they are not frameworks. I know this probably just seems like a semantics issue, but I want to make it clear that they are not frameworks, they are libraries. From http://dictionary.reference.com/browse/framework
    read
    • posted 2½ years ago

    Script/Asset abuse: this is getting ridiculous!

    Abuse_is_badFrameworks like YUI, JQuery, Mootools, Dojo, etc., are arguably the best thing to have happened to JavaScript in 10 years. I remember when I first learned about their existence. I was coding my own animation script (functional, not OO, and definitely not efficient) that didn't do anything fancy; just scrolled up and down. I remember then hearing about dojo, and thinking I'd wasted so much time.

    Then what I did, was go around to all the different frameworks. I don't even think JQuery existed in it's current incarnation at that point (December of 2005), and I looked around at as many as I could (dojo, mootools, and a few others that have since become relics). This post though, isn't about the greatness of these frameworks; rather it's about the terrible abuse.
    read