Skip to main content

Importance of Community support when evaluating open source software

In my previous company we were evaluating ExtJS v/s SmartClient, we did lots of comparisons and SmartClient had lots of cool features and was up to the par with ExtJS but the only thing that was lacking here was traction in the community, finally we decided on ExtJS. When evaluating an open source product I give lots of importance to open source community around that product, namely I look for
  1. Does this product has a mailing list, how active is the mailing list? how many messages are posted by users per month and are there enough discussions going on?
  2. How frequent are releases for this product?
  3. How many users have written blogs and tutorials about this product?
  4. Are there any books from OReilly or Manning about this product (I rate Manning and Oreilly books better then other and I hate the SAMS 24 days books)
  5. How many bugs are closed,Open,In QA for this product
  6. How old is this product? Old product have their own baggage so if a newer kid is on the block with a vibrant community I would compare features and go for it.
That is the same reason I would prefer ExtJs over SmartClient, Struts over JSF, Hibernate over JDO.

Comments

  1. To make a correct assessment of this kind you have to understand the potential community size. SmartClient targets specifically high end enterprise web applications. Ext is used for lightweight applications and minor augmentation of otherwise static content. There are many many more simple websites than enterprise web applications.

    If you're trying to build an enterprise web application and you choose a product because there are a bunch of people using it for something entirely different, then what you've just done is set yourself up to wade through noisy forums and inappropriate tutorials and examples that don't address your use case.

    As with many products that target the high end, the SmartClient community has a very high percentage of enterprise architects. Ask a very hard question and you will often get a very astute answer. That's what counts.

    ReplyDelete
  2. Charles,

    First of all Thanks for the comment. I recently started blogging so nice to have some feedback.

    Now coming to the point, well saying ExtJS is not sufficient for Business applications is a an understatement. I was working for an On demand supply chain application (www.onenetwork.com) and they are using ExtJs and customers love it. I recently moved to an Online file sharing and backup company and guess what they are also using ExtJS and have lots of customers loving it.

    As I said in my post already SmartClient had lots of better features and it was at par in terms of features in comparison to ExtJS. The only reason to pickup ExtJS was community support and in last 1 year it has seen explosive growth. (I still hate that ExtJS started charging license fees for using them). I compared and saw that ExtJS community was far more vibrant and active then ExtJS.

    Regards
    -Kalpesh

    ReplyDelete
  3. Hi Kalpesh,

    Can't really make out what you're saying - you say that Ext is not sufficient for business applications, but then that end users liked it. But end users see a product, they are not evaluating Ext vs SmartClient, so that didn't make much sense. Did you mean the customers liked the themes? That was a common complaint with SmartClient before the new themes. We don't hear that complaint now.

    Elsewhere you say the Ext community is more vibrant than the Ext community.. maybe a typo there too.

    Just to recap, it doesn't matter how many members there are in the community, it matters how many members are *doing what you're doing*. I would say, and many others have noted, that Ext has far fewer users building complex, high end business applications.

    But for many companies, the decision can also be made on the basis of features. If you go through the examples on the SmartClient site vs Ext's, there is plainly a massive feature advantage in SmartClient's favor, which we also show here:

    http://smartclient.com/product/competition.jsp

    So an evaluator needs to go through their requirements and find out how much more they get out of the box with SmartClient, and especially they need to think about what features they might want to leverage in version 2.0 of their product.

    Because a bunch of people chatting vibrantly about the lack of a feature in Ext also does not help you deliver an application :)

    ReplyDelete

Post a Comment

Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are
Download ErlangDownload Rabbit MQ ServerDownload Rabbit MQ Java client jarsCompile and run the below two class and you are done.
This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time.

For more information on AMQP, Exchanges, Queues, read this excellent tutorial
http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/

+++++++++++++++++RabbitMQProducer.java+++++++++++++++++++++++++++
import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost("127.0.0.1"); factory.setPort(5672); Conne…

Logging to Graphite monitoring tool from java

We use Graphite as a tool for monitoring some stats and watch trends. A requirement is to monitor impact of new releases as build is deployed to app nodes to see if things like
1) Has the memcache usage increased.
2) Has the no of Java exceptions went up.
3) Is the app using more tomcat threads.
Here is a screenshot

We changed the installer to log a deploy event when a new build is deployed. I wrote a simple spring bean to log graphite events using java. Logging to graphite is easy, all you need to do is open a socket and send lines of events.
import org.slf4j.Logger;import org.slf4j.LoggerFactory; import java.io.OutputStreamWriter; import java.io.Writer; import java.net.Socket; import java.util.HashMap; import java.util.Map; public class GraphiteLogger { private static final Logger logger = LoggerFactory.getLogger(GraphiteLogger.class); private String graphiteHost; private int graphitePort; public String getGraphiteHost() { return graphiteHost; } public void setGraphite…

Jersey posting multipart data

This took me sometime to figure out mostly it was because I was only including jersey-multipart-1.6.jar but I was not including mimepull-1.3.jar.

So the intent is to upload a file using REST api and we need pass meta attributes in addition to uploading the file. Also the intent is to stream the file instead of first storing it on the local disk. Here is some sample code.
@Path("/upload-service") public class UploadService { @Context protected HttpServletResponse response; @Context protected HttpServletRequest request; @POST @Consumes(MediaType.MULTIPART_FORM_DATA) @Produces(MediaType.APPLICATION_JSON) public String uploadFile(@PathParam("fileName") final String fileName, @FormDataParam("workgroupId") String workgroupId, @FormDataParam("userId") final int userId, @FormDataParam("content") final InputStream content) throws JSONException { //.......Upload the file to S3 or netapp or any storage service } }
Now to tes…