Today
Google Chrome was released. I had never heard of it in fact before today, though I suspect most others had neither so I don't really feel embarassed for that. My first reaction was probably not that different from most other Ajax Library vendors in this world. I instantly rushed to check out our
online Ajax Samples to see if Ra-Ajax could put up with the Chrome.
The importance of Open Standards
And I can say immediately that
Ra-Ajax works perfect with Google Chrome. :)
In fact if it didn't I would be surprised. Since we're focusing a lot of energy on being 100% conforming towards the Open Web Standards as given to us from the
W3C. I am willing to bet parts of my body that the developers at Google payed ZIP attention to being
"Ra-Ajax compatible" when developing Google Chrome. Ra-Ajax was released only a couple of weeks ago, and except for us I don't think I know about more than a handful of people who claims to be using it today ;)
The secret behind this of course is the Open Standards. HTML, CSS and JavaScript. By following them religiously Ra-Ajax completely delivered in regards to a technology we in Ra-Software had not foreseen and not anticipated or even had wild dreams about. In fact I was completely sure of that Google would "stay away" from browsers themselves due to the battle-field currently being filled with blood from developers at Mozilla, Opera, Safari and to some extent even MSFT. In fact even our
Rich Editor seems to even work flawlessly with Google Chrome. Oh yeah and we did NOT have to create an "emergency release" to support Google Chrome. Today we are HAPPY!
Though I suspect not all Ajax Library developers feels equally happy about Google Chrome today... ;)
The logical conclusion however for all the developers in this world creating Ajax Libraries, CSS Frameworks, JavaScript Frameworks and so on I hope is to embrace the Open Standards given to us from W3C and not take their chances with "extensions that currently seems to work" like adding "custom attributes", starting ID elements with non-alpha characters or having block-level elements inside of inline-elements etc.
I hope Ajax "wins", though if we should win we must use our biggest weapons. Currently our biggest weapon is the Open Web with JS, HTML, CSS and following them to the last letter as given to us by W3C. If we don't we loose our greatest advantage which is that "our stuff just works on bloody everything"...
Ajax rules!
Embrace the Open Web!
Don't make the next browser Update be another "nightmare day"!
Follow the Open Standards from W3C!!!!!
Comments