Skip to main content

Success of Open Source Projects : all hail Spring

What makes an Open Source Project successful? When I started web frameworks with Struts 1.1 in 2004, I had a VERY hard time learning the framework. People who have been in the same boat would remember these key words "Struttin' with Struts" which would google to Rick Reumann's 4 or 5 chapter tutorial - that was by far the only DECENT tutorial available at that time. There may be more now, but I am not in the hunt.

At around the same time, Spring was coming up. And boy did it catch up like fire. The success story highlighted the importance of documentation. Rod Johnson's Team got it right in the first time. They realised that the popularity of an opensource project is directly proportional to the quality and quantity of its documentation. Ever since, you can see there are tons documentation for anything they release, in its own space. These include a lot of examples, code framgments etc. They still need centralise the individual projects to the main documentation page. Still, I think they are doing a good job.

So there you go, I let you out this little secret.. Good Documentation is well recieved.

Leave comments in Guestbook

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery

Decorator for Memcache Get/Set in python

I have suggested some time back that you could modularize and stitch together fragments of js and css to spit out in one HTTP connection. That makes the page load faster. I also indicated that there ways to tune them by adding cache-control headers. On the server-side however, you could have a memcache layer on the stitching operation. This saves a lot of Resources (CPU) on your server. I will demonstrate this using a python script I use currently on my site to generate the combined js and css fragments. So My stitching method is like this @memize(region="jscss") def joinAndPut(files, ext): res = files.split("/") o = StringIO.StringIO() for f in res: writeFileTo(o, ext + "/" + f + "." + ext) #writes file out ret = o.getvalue() o.close() return ret; The method joinAndPut is * decorated * by memize. What this means is, all calls to joinAndPut are now wrapped (at runtime) with the logic in memize. All you wa...

Faster webpages with fewer CSS and JS

Its easy, have lesser images, css and js files. I will cover reducing number of images in another post. But If you are like me, You always write js and css in a modular fashion. Grouping functions and classes into smaller files (and Following the DRY rule, Strictly!). But what happens is, when you start writing a page to have these css and js files, you are putting them in muliple link rel=style-sheet or script tags. Your server is being hit by (same) number of HTTP Requests for each page call. At this point, its not the size of files but the number server roundtrips on a page that slows your page down. Yslow shows how many server roundtrips happen for css and js. If you have more than one css call and one js call, You are not using your server well. How do you achieve this? By concatinating them and spitting out the content as one stream. So Lets say I have util.js, blog.js and so.js. If I have a blog template that depends on these three, I would call them in three script tags. Wh...