Open Source AJAX toolkits
twofish writes "InfoWorld columnist Peter Wayner recently reviewed six
of the most popular "open source" Ajax toolkits. The article sets
out to see if they are enterprise ready in comparison to commercial products
such Backbase, JackBe, and Tibco's General Interface. The six open source projects
covered were selected because each has a high-profile in the developer community
and support of one or more stable organizations. "
The toolkits covered are:
Whilst the definition of open source is broad, the round-up is quite helpful.
- Dojo
- Google Web Toolkit
- Microsoft Atlas
- Open Rico and Prototype
- Yahoo AJAX Library
- Zimbra Kabuki AJAX Toolkit
Whilst the definition of open source is broad, the round-up is quite helpful.
This is in response to Google's toolkit, which allows users to code in Java instead of Javascript. I think this feature is a real winner to Java coders. Who wants to code Javascript when you can use Swing? Regardless of what TFA says, there is a difference between the two programming experiences.
In summary, if you are already proficient in Java, Google is the way to go.
Information wants a fueled airplane waiting at the hangar and no one gets hurt.
The only reason large corporations push some toolkit as "open source" is because:
1. It's a crappy product that their marketing people cannot justify as promotion cost
2. There are better free products
3. They are trying to get their foot into the niche so they can then charge for the "Professional" version
4. They don't understand the space yet
This is common for Microsoft and now becoming common for Google.
Sadly AJAX is still the "silver bullet" of web based companies and the buzzword of the moment. So many companies are using AJAX for the sake of using it despite the fact it is not applicable to the ir use case; sometimes it is easier to wedge something in and use a buzzword to sound cool and relevant.
and for all other effects write your own functions just like always (copy/paste from your personal library and adapt)
Or you just do exactly what digg does and take your own javascript library and include everything you possibly can do "just in case".
I'm actually surprised kitchenSink.js isn't included.
This is just an example from the standard front screen of digg without any cookies or logins to concern itself with.
<script src="/js/spellChecker.js" type="text/javascript"></script>
<script src="/js/utils.js" type="text/javascript"></script>
<script src="/js/xmlhttp.js" type="text/javascript"></script>
<script src="/js/comments.js" type="text/javascript"></script>
<script src="/js/wz_dragdrop.js" type="text/javascript"></script>
<script src="/js/hover.js" type="text/javascript"></script>
<script src="/js/label.js" type="text/javascript"></script>
<script src="/js/dom-drag.js" type="text/javascript"></script>
<script src="/js/switcher.js" type="text/javascript"></script>
<script src="/js/prototype.js" type="text/javascript"></script>
<script src="/js/scriptaculous.js" type="text/javascript"></script>
<script src="/js/lightbox.js" type="text/javascript"></script>
<script src="/js/aboutdigg.js" type="text/javascript"></script>
liqbase