Clojure
Rich Hickey discusses Clojure features and syntax, example code, functional programming, concurrency semantics, transactions, software transactional memory, agents, implementation and pain points.
- Java,
Tracking change and innovation in the enterprise software development community
Posted by Alexander Olaru on Dec 06, 2007 01:00 PM
With the continuous growth of AJAX technologies adoption, many developers and architects are still trying and sometimes struggling to determine what are the best ways to evaluate Java Script frameworks/libraries. Brian Raindel offered some advice on the various aspects one should consider during the selection process, summarized here:Beware of these frameworks if your app requires high performance. Prototype, jQuery fall over terribly when using large tables and grids.Another commenter pointed out that Mootools has a page benchmarking Protoype, JQuery & Mootools.
I’ve done extensive benchmarking for my current project at work which is very AJAX heavy and will use at it’s core large tables.
I’ve experimented with both jQuery and Prototype and the performance was always lacking. The problem? document.getElementById(). DOM lookup is VERY expensive. In fact, our tests seem to suggest that DOM lookup is not done via hashing.
A lot of these frameworks add extensions that many times you will not need, slowing performance down. Our solution has been to study what is beind done and write our own code, minus all the extensions and any extraneous framework support it is doing.
But for small webpages without large tables, Prototype or jQuery work very well and are nice to work with.
Creating Rich Internet Applications with the Adobe Technology Platform
This is great stuff - but why only Javascript. This would seem to apply to all things...especially open-source.
beren
It's an interesting list, but it seems to leave out one of the single most important evaluation criteria: whether the framework leans toward unobtrusive or obtrusive JavaScript.
For instance, ExtJS tends to be highly obtrusive, but suitable for some people who don't mind coding lots of their interface in JavaScript rather than HTML.
On the other hand, jQuery and Prototype, and their UI plugins, tend toward unobtrusiveness. Or at least you have more of an option on how obtrusive you'd like to be.
This is not to point out those frameworks, but rather the glaring omission from the article above.
?? He gives a bunch of generic criteria, most of which _do_ apply when selecting any type of framework. The he doesn't really give any answers, other than "Prototype and JQuery can be slow." So I guess that means Dojo, YUI, ExtJS and MooTools are faster?? We don't know because the whole thing was kind of lacked detail. Other than where he wrote that they re-wrote the framework with just the parts they needed. That doesn't really seem like framework selection to me. That sounds more like "roll your own JS framework."
We can use the part of the jQuery function.
If Prototype & jQuery aren't suited for Ajax heavy applications, then what should we use?
@ Hussein: you could take a look at Dojo, Tibco and Backbase. Those are some of the more comprehensive Ajax frameworks.
Rich Hickey discusses Clojure features and syntax, example code, functional programming, concurrency semantics, transactions, software transactional memory, agents, implementation and pain points.
We introduce the concept of Composite Oriented Programming, and show how it avoids the issues with OOP and reignites the hope of being able to compose domain models with reusable pieces.
Dan Farino talks about the system architecture and the challenges faced when building a very large online community. Dan explains how a .NET product scales on hundreds of servers.
Alan Shalloway, CEO and founder of Net Objectives, presents the Lean software development principles and practices and how they can benefit to Agile practitioners.
Bernd Mathiske discusses Maxine VM, Java compatibility, swapping major VM components, research areas, Object handling, code examples, optimizing compiler, snippets, bytecode generation, JNI and JIT.
Joe Armstrong speaks on various aspects of the Erlang language, presenting its roots, how it compares with other languages and why it has become popular these days.
The java double-check singleton pattern is not thread safe and can’t be fixed. In this article, Dr. Alexey Yakubovich provides an implementation of the Singleton pattern that he claims is thread-safe.
Diana and Jim talk about patterns observed in CTOs' activity. CTOs emerge as real people caring for other people in their organization, and are put under a lot of pressure and constraints.
6 comments
Reply