Comment 1 for bug 705481

This would indeed be nice and many other have asked for it already.

Options I see to get the data:
 - The cheapest method to achieve this would be to collect just a few indicators for programming language based on the debian/control File data (Build-Depends of the the source, names of resulting binary packages) and in the UI be clear that this is just a wild guess.
 - More "expensive" would be to check out the source itself and use something like libmagic or sloccount to figure out what kind of programming language we talk about.

A few other thoughts of the top off my head:
 - In any case we need to change the database schema.
 - I think I'd prefer external data providers to get us package information (JSON too, we could have stuff like popcon position, etc. too). Let's try to make Harvest not too clever to keep the scope focused.
 - We should give users the opportunity to correct the programming language "suggestions".