The Web Is In Danger...because of "non standard AJAX"..Oh my..
PERMALINK || External link to topic of post
When is a non-standard a standard? AJAX? Wasn't it a non-standard from Microsoft?
Brief on it's history:
So lets get this straight, something that Microsoft created, is in danger if they "push it" somewhere?
Don't get me wrong, I know exactly what standards mean, and yes, sticking to them does make everyone a nice neighbor. But please, the idea that nobody can "fork" things elsewhere, whether it be suicidal, or actually creates a non-standard-today-but-renamed-standard-tomorrow, is utter crapola. XMLHttp may not be a sexy as AJAX, but it's roots are in the proprietary, non-standard world.
Brief on it's history:
"AJAX is not actually that new as a technology. It has been first used after Microsoft implemented Microsoft.XMLHTTP COM object that was part of The Microsoft® XML Parser distributive. As an ActiveX object in Internet Explorer 5, it was used to create the famous Outlook Web Access. You have probably seen AJAX in action for quite long in the MSDN Documentation treeview navigation.
What is new actually is the name AJAX, which was widely accepted in 2005. Other labels for the same technology are Load on Demand, Asynchronous Requests, Callbacks, Out-of-band Calls, etc. "
So lets get this straight, something that Microsoft created, is in danger if they "push it" somewhere?
Don't get me wrong, I know exactly what standards mean, and yes, sticking to them does make everyone a nice neighbor. But please, the idea that nobody can "fork" things elsewhere, whether it be suicidal, or actually creates a non-standard-today-but-renamed-standard-tomorrow, is utter crapola. XMLHttp may not be a sexy as AJAX, but it's roots are in the proprietary, non-standard world.


0 Comments:
Post a Comment
Links to this post:
Create a Link
<< Home