Summary for those in a hurry:
"fuck this, fuck that shit, dojo has better i18n and a11y plugins, fuck jquery, The End"
The tarantino writing style weakens his argument, IMHO. More scientific arguments and less passion please.
Rebecca, thank you for posting these. I'd categorize myself among the n00bs the OP refers to, and your reasoned articles were very beneficial. I hadn't considered Dojo in the past, but I'm planning a very client-heavy JavaScript application in the near future, and I'll definitely check it out.
If you're calling i18n and a11y "plugins", you're missing the point. These types of considerations are taken thoughout the framework in a consistent manner.
Comments
Summary for those in a hurry: "fuck this, fuck that shit, dojo has better i18n and a11y plugins, fuck jquery, The End" The tarantino writing style weakens his argument, IMHO. More scientific arguments and less passion please.
Perhaps these will be sufficiently dispassionate for you:
- http://blog.rebeccamurphey.com/on-rolling-your-own
- http://blog.rebeccamurphey.com/on-jquery-large-applications
- http://blog.rebeccamurphey.com/2009/11/12/dojo-confessions-o...
Rebecca, thank you for posting these. I'd categorize myself among the n00bs the OP refers to, and your reasoned articles were very beneficial. I hadn't considered Dojo in the past, but I'm planning a very client-heavy JavaScript application in the near future, and I'll definitely check it out.
I would look at MooTools, their approach to OO JS abstraction keeps your JS heavy web apps lean and mean!
If you're calling i18n and a11y "plugins", you're missing the point. These types of considerations are taken thoughout the framework in a consistent manner.