Thanks

<p>Hey Odd,</p> <p>Thank you very much for your post and your kind comments. We might just turn your post into a testimonial ;)</p> <p>I think you've more less hit the nail on the head in terms of this site. Technologically we hope CodeCogs is one of the more advanced systems out there and we've certainly invested a lot of effort to get it right. The issue we face at the moment is have we designed something that solve our issues with code organisation (see About), or is this something that interests the wider community. Currently CodeCogs has over fourteen hundred authenticated users. We almost exactly double is size both in terms of daily traffic, signups, downloads and user-base every 6 weeks. So we are moderately confident we're doing something right. However we need people to tell us what else we should do..</p> <p>Over the next month we'll be ramping up our marketing effort by submitting articles about CodeCogs to a range of technical journals and computer presses (see for example http://www.codecogs.com/pages/excel/example1.html , which was published by Lloyds of London).Ultimately though we are prepared for the long haul battle to get CodeCogs right and get our users involved in its creation.</p> <p>What can you do?</p> <p>  a) Publish your best C/C++ module.<br />   b) Send us your feedback on using the system (publishing, downloading etc).<br />   c) Publish more of your best code. <br />   d) Publish corrections to existing modules. <br />   e) Publish more of your code :) (remember you can publish it for free or for commercial use and you can even keep it in a private folder..) <br />   f) When we turn on the Wiki style editing of reference pages (in about 2-3 weeks), then help us edit these (mainly to incorporate working Example). <br />   g) Post this site on your personal web-pages, tell your friends about us, write about us in other forums, get your company to link to us, etc... <br />   h) Publish more comments to the forum. <br />   i) Search for bugs in the system (they are out there somewhere...).<br />   j) Keep sending up positive vibes - they really will help us keep going now that winter is setting in :)</p> <p>Supporting Other languages...</p> <p>As for your suggestion about allowing other languages. We're on the case. Its been one of the most common statements we've received. The trouble is you have to start somewhere, so C/C++ it was. In the new year we do plan to port our engine to Java, C#, Pascal and even Fortran. However we need to prove the concept works first with C/C++ before we get too carried away. We are also thinking very hard about how we package all these language, i.e</p> <p>  - A new web site for each language, i.e. CodeCogs/java; CodeCogs/pascal etc <br />   - or Keep with once central site, beef up the search engine and have a language option on each page which lists all the languages that one particular module is distributed under. <br />   - some bastardisation of the two.</p> <p>The second option is much harder and potentially much more confusing for the users, but potentially smoother. What do you think? But fundamentally, we don't have the time to rewrite all this software in a dozen languages, so until we feel confident that other users are prepared to help us grow all these systems, then we'll be focussing our own efforts on C/C++..</p> <p>Keep in touch, Will.</p>