Talk:Ajax Framework: Difference between revisions
imported>Pat Palmer (subpages) |
imported>Michael Bonanno |
||
Line 3: | Line 3: | ||
== Don't agree with the premise of this article == | == Don't agree with the premise of this article == | ||
I'm acquaintances with a fair few front-end web developers, and I rarely ever hear them talk about "AJAX frameworks" (first of all, because "AJAX" is usually "Ajax") - instead they talk about "JavaScript frameworks". Which makes a ton more sense, since the stuff which you most need to hide away behind a framework isn't usually the XMLHttpRequest object but all the other cross-browser crud. I suggest we quickly move this page to "JavaScript framework", and also not include ''any'' library-specific code, which should probably be on the pages for the relevant libraries: [[Dojo (framework)]], [[jQuery]], [[Prototype (framework)]], [[script.aculo.us]], [[MooTools]], [[Yahoo! UI Library]], [[Rico (framework)]] etc. --[[User:Tom Morris|Tom Morris]] 17:48, 10 August 2008 (CDT) | I'm acquaintances with a fair few front-end web developers, and I rarely ever hear them talk about "AJAX frameworks" (first of all, because "AJAX" is usually "Ajax") - instead they talk about "JavaScript frameworks". Which makes a ton more sense, since the stuff which you most need to hide away behind a framework isn't usually the XMLHttpRequest object but all the other cross-browser crud. I suggest we quickly move this page to "JavaScript framework", and also not include ''any'' library-specific code, which should probably be on the pages for the relevant libraries: [[Dojo (framework)]], [[jQuery]], [[Prototype (framework)]], [[script.aculo.us]], [[MooTools]], [[Yahoo! UI Library]], [[Rico (framework)]] etc. --[[User:Tom Morris|Tom Morris]] 17:48, 10 August 2008 (CDT) | ||
<a href='http://www.google.com/trends?q=Ajax+framework%2C+javascript+library%2C+javascript+framework&ctab=0&geo=all&date=all&sort=0'> The google no lie</a>. Just as many people are using the term 'Ajax Framework' as 'JavaScript Library', although 'Javascript Library' is gaining popularity. But of course a Javascript Library does not connote the same thing as "Ajax Framework". A Javascript library may be any grouping of Javascript Functions, for any small purpose. The term 'Javascript Framework' does connote the same thing as the first two classes of Ajax Frameworks that I have described, however it is not nearly as widely used.[Refer to the Google link] However, it doesn't not adequately describe the set of "frameworks" that create Ajax web pages through server-based coding. The most prominent of these is Asp.net AJAX. Asp.net AJAX, and PHP based things like SAJAX are "Ajax Frameworks", but not "Javascript Frameworks". The most proper term for this article would be "Cross-Browser Rich Internet Application Framework" however NO ONE would ever search for that. Yes there is some ambiguity here, but the existence of the term Ajax Framework is not one of those ambibuities. | |||
--[[User:Michael Bonanno|Michael Bonanno] 12:48, 15 August 2008 (CDT) | |||
==might as well list them ALL== | ==might as well list them ALL== | ||
article would benefit from an updated something like the one found here: http://www.infoq.com/news/ajaxian-survey | article would benefit from an updated something like the one found here: http://www.infoq.com/news/ajaxian-survey |
Revision as of 22:44, 15 August 2008
Don't agree with the premise of this article
I'm acquaintances with a fair few front-end web developers, and I rarely ever hear them talk about "AJAX frameworks" (first of all, because "AJAX" is usually "Ajax") - instead they talk about "JavaScript frameworks". Which makes a ton more sense, since the stuff which you most need to hide away behind a framework isn't usually the XMLHttpRequest object but all the other cross-browser crud. I suggest we quickly move this page to "JavaScript framework", and also not include any library-specific code, which should probably be on the pages for the relevant libraries: Dojo (framework), jQuery, Prototype (framework), script.aculo.us, MooTools, Yahoo! UI Library, Rico (framework) etc. --Tom Morris 17:48, 10 August 2008 (CDT)
<a href='http://www.google.com/trends?q=Ajax+framework%2C+javascript+library%2C+javascript+framework&ctab=0&geo=all&date=all&sort=0'> The google no lie</a>. Just as many people are using the term 'Ajax Framework' as 'JavaScript Library', although 'Javascript Library' is gaining popularity. But of course a Javascript Library does not connote the same thing as "Ajax Framework". A Javascript library may be any grouping of Javascript Functions, for any small purpose. The term 'Javascript Framework' does connote the same thing as the first two classes of Ajax Frameworks that I have described, however it is not nearly as widely used.[Refer to the Google link] However, it doesn't not adequately describe the set of "frameworks" that create Ajax web pages through server-based coding. The most prominent of these is Asp.net AJAX. Asp.net AJAX, and PHP based things like SAJAX are "Ajax Frameworks", but not "Javascript Frameworks". The most proper term for this article would be "Cross-Browser Rich Internet Application Framework" however NO ONE would ever search for that. Yes there is some ambiguity here, but the existence of the term Ajax Framework is not one of those ambibuities.
--[[User:Michael Bonanno|Michael Bonanno] 12:48, 15 August 2008 (CDT)
might as well list them ALL
article would benefit from an updated something like the one found here: http://www.infoq.com/news/ajaxian-survey