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.
Labels:

Comments

  1. Charles KendrickDecember 19, 2009 at 3:42 PM

    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. Kalpesh PatelDecember 20, 2009 at 6:39 PM

    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. Charles KendrickDecember 22, 2009 at 6:24 PM

    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

Haproxy and tomcat JSESSIONID

One of the biggest problems I have been trying to solve at our startup is to put our tomcat nodes in HA mode. Right now if a customer comes, he lands on to a node and remains there forever. This has two major issues: 1) We have to overprovision each node with ability to handle worse case capacity. 2) If two or three high profile customers lands on to same node then we need to move them manually. 3) We need to cut over new nodes and we already have over 100+ nodes.  Its a pain managing these nodes and I waste lot of my time in chasing node specific issues. I loath when I know I have to chase this env issue. I really hate human intervention as if it were up to me I would just automate thing and just enjoy the fruits of automation and spend quality time on major issues rather than mundane task,call me lazy but thats a good quality. So Finally now I am at a stage where I can put nodes behing HAProxy in QA env. today we were testing the HA config and first problem I immediat...
Post a Comment
Read more

Adding Jitter to cache layer

Thundering herd is an issue common to webapp that rely on heavy caching where if lots of items expire at the same time due to a server restart or temporal event, then suddenly lots of calls will go to database at same time. This can even bring down the database in extreme cases. I wont go into much detail but the app need to do two things solve this issue. 1) Add consistent hashing to cache layer : This way when a memcache server is added/removed from the pool, entire cache is not invalidated.  We use memcahe from both python and Java layer and I still have to find a consistent caching solution that is portable across both languages. hash_ring and spymemcached both use different points for server so need to read/test more. 2) Add a jitter to cache or randomise the expiry time: We expire long term cache  records every 8 hours after that key was added and short term cache expiry is 2 hours. As our customers usually comes to work in morning and access the cloud file server it ...
Post a Comment
Read more

Spring 3.2 quartz 2.1 Jobs added with no trigger must be durable.

I am trying to enable HA on nodes and in that process I found that in a two test node setup a job that has a frequency of 10 sec was running into deadlock. So I tried upgrading from Quartz 1.8 to 2.1 by following the migration guide but I ran into an exception that says "Jobs added with no trigger must be durable.". After looking into spring and Quartz code I figured out that now Quartz is more strict and earlier the scheduler.addJob had a replace parameter which if passed to true would skip the durable check, in latest quartz this is fixed but spring hasnt caught up to this. So what do you do, well I jsut inherited the factory and set durability to true and use that public class DurableJobDetailFactoryBean extends JobDetailFactoryBean {     public DurableJobDetailFactoryBean() {         setDurability(true);     } } and used this instead of JobDetailFactoryBean in the spring bean definition     <bean i...
7 comments
Read more