why another javascript framework?
I know, I know. Why!? But in truth, why not? I’m always complaining about something in each and every framework I’ve used. They all have good, bad and incomplete (at least to me) parts. I want to merge everything I love about every framework I’ve used and then some to see what the outcome is.
The main reasons though, are as a learning exercise and because I want to work on a project where quality comes before profit. I am a pretty good at writing HTML, CSS and JavaScript, as well as UI application architecture and design. I have written mini-frameworks and UI frameworks that sit on top of existing frameworks, like prototype and MooTools for various projects I have worked on in the last 5 years. There’s always more to learn and there’s no better way of doing it that diving into the deep end.
As a work of quality: I’ve worked on one project after another in the almost 5 years since I moved to London which involved me being used as a paddle to get whoever out of shit creek. Research and development, unit testing, functional testing, retrospectives and basically doing anything except coding like a madman and the like have all been seen as massive wastes of resource, time and money by past employers, with the exception of the BBC, where it can and has been taken to the other extreme.
You can only do that for so long before you burn out, so I want to do something that I AM proud of for once.
It’s either that, or have a nervous breakdown. :¬P
