Going Simple with JavaScript – Snook.ca.
I can’t begin to explain how ‘up my alley’ this post from Jonathan Snook was this morning. Over the past few weeks I’ve been researching (and posting what I’ve been reading) insofar as what I would consider bleeding edge JavaScript frameworks for more advanced app development.
The whole time I couldn’t help but look at the payloads associated with these frameworks. The whole point of the modern Web is to be open & agile, right? Megabytes of JavaScript don’t provide that in my opinion.
Jonathan takes us back to our roots, but our modern roots. In his example he saves himself around 90,000 bytes simply by taking the time to implement a bit of JavaScript by hand instead of instinctively relying on jQuery. Love it.
Comments
Oh man, I just recoded a project that spagetti jQuery (you know a million .parent() calls, to try and read data from text inputs) with Knockout.
What a difference. Not only are things more organized, but my code is much shorter.
Of course, ALL of the code for the project is longer (because I’m including the Knockout library!) but the project code itself is much smaller. I would imagine the returns multiply exponentially as a project gets more intricate.
In addition… I suppose that it might make things smaller to try and make my own MVC framework for a project, but there’s something to be said for speed, and having they standards of other other (and better coders than me) to lean on.