Al Sutton
Tue, 22 Jul 2008 23:04:57 -0700
Personally I use YUI for two reasons;1) It's easy to separate out and include only the parts I need in my webapp so I don't end up with war bloat.
2) The mailing lists seemed reasonably active. Al. Martin Cooper wrote:
On Tue, Jul 22, 2008 at 3:57 PM, Ted Husted <[EMAIL PROTECTED]> wrote:Dojo seems to get the most lip service, but I've seen persistence reports that YUI has broader acceptance.The thing is, it depends a whole lot on what you are doing with it. For example, the people I know who are developing rich client-side apps with JavaScript are using Ext JS or Dojo. None of them are using YUI because YUI simply isn't appropriate, or complete enough, for that kind of usage. It's perfectly fine, though, if what you want is to add some AJAXy capabilities to a more traditional web app. As another example, there are certainly plenty of people building point applications with Prototype and its friends, but if you're building something that needs to be extensible and include components from elsewhere, you almost certainly don't want to be using a framework that messes with core JavaScript types. -- Martin Cooper-Ted. On Tue, Jul 22, 2008 at 4:48 PM, Dave Newton <[EMAIL PROTECTED]> wrote:--- On Tue, 7/22/08, Paul Benedict <[EMAIL PROTECTED]> wrote:Isn't Dojo the defacto ajax standard on the web?In terms of deployments I'd put money on Prototype and/or jQuery. Notthat it's a large sample size, but I don't know *anybody* using Dojo outside of S2.Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]-- HTH, Ted http://husted.com/ted/blog/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]