We just rolled out an update to our public site, with some key improvements:

• Better code index We added over 20,000 new projects, including many that are archive-only (no code available in a public SCM) from repositories such as SourceForge.net and Tigris. We now have over 2 billion lines of code in our index.
• New languages We now support Erlang and Groovy. I’m guessing Yonatan and Al, among others, will be very excited about this. I know, we’re still missing ABAP, Forth, SCL, LabVIEW, etc, etc. Good God there are a lot of programming languages out there!
• Revised Eclipse IDE plug-in The Eclipse plug-in is now at version 1.0.5.2, and recently passed the Ready for Rational gauntlet. You can download the latest version here. This link is still to the beta program page, but we’re transitioning to general availability.
• Open API A big part of this release was cleaning up the RESTful API to our services, in preparation for public availability. If you’re interested, send email to support@krugle.com and request to be added to the documentation seed list.
• Lots of cleanup For example, our code query parser is smarter about quoted terms. You can click on language graphs in a project page (like KDE). And many more fixes and features requested by our users - so keeping clicking that feedback link…it really works!
• Top Projects As always, we continue to expand our list of top projects.

While the size of the index isn’t so important (see my early blog post on 1,563,644,824 reasons why size doesn’t matter), the fact that it’s grown by over 35% in the past 6 weeks is an important data point. We’re finding that the long tail of public code is longer and fatter than we thought. The rate at which we find new repositories and projects, as well as the rate at which new projects get added to existing repositories, isn’t slowing down. And as more companies decide to open up their source code, I expect to see an accelleration in the growth of public code.

Notice that I’m using the term “public code” instead of “open source software”. Another trend (for a future blog) is that we’re seeing an increasing amount of code released under what I call “look but don’t touch” licenses. Or maybe a better term would be “antique store” licenses, as in “you use it, you pay for it”. More on that later.

Getting back to the recent update to Krugle, I’m excited about opening up our API. You’ve been able to send in search requests and project links (via URLs) for quite a while - see this blog post by Chris Burmester from last October. What we’re doing now is providing public access to the back end APIs that actually power the Krugle web site and our Eclipse IDE plug-in. Using this API, you’ll have access to the same code, tech pages, and project data that you see on the public web site and via the Eclipse IDE plug-in.

So send us email if you’d like to get added to the documentation seed list (once again, that’s support@krugle.com), and include a short description of how you’re thinking of using the API.

Thanks,

– Ken, Krugle Blog

Tags: Groovy