November 25, 2006
Is Java bad? Ask Ajaxian…
Christian Decker wrote this at around evening time:
Ajaxian has once again a new Post about a new Library, this time a URL Parser. All nice and shiny but it isn’t the library I want to write about, it’s the finishing comment they put in there:
Also interesting posts:This smells like a Java group writing JavaScript to me with the camelCase and thus p.getUsername() instead of p.username.Why should it be negative to immitate Java? I’m a Java-Programmer myself and I try to use as much as I can from my experience when writing Ajax applications. I think the Ajax community could learn a lot from the Java style of doing things instead of being so snobbish…
- Java, a retrospective
- Google Web Toolkit - Performance and Interoperability
- XML11: An Abstract Windowing Protocol
- Sxip contributes Java and Perl libraries to OpenID 2.0
- Aine: AJAX is not everything…
November 26th, 2006 at 00:12:02
Personally — I’d have to do some research to back this up — I think that much of JavaScript’s rise to power (and web 2.0 in general) in the last year or two has had much to do with the development of superb APIs. After all, not much has changed on the browser-side. Java developers probably understand better than most how to create well-written & documented APIs.
For example, look at Jack Slocum’s incredible YUI-EXT library. It is clearly influenced by Java idioms, as he is also a Java developer.
November 26th, 2006 at 12:03:48
It wasn’t my goal to upset anyone, just put things right, that Java isn’t bad, and Ajax isn’t always good…
November 26th, 2006 at 18:10:37
November 28th, 2006 at 21:38:11
p.s. lets don’t forget that every language have its unique abilities whitch the other language don’t have.
February 2nd, 2007 at 19:09:33