In order to get started with biicode and support our open source project we launched a while back a our Darth Vader++ campaign in which anyone that uploaded any piece of code to our cloud and had it reused by any other user would receive for free our Darth Vader++ t-shirt. The campaign has been a huge success, many libs and frameworks have been uploaded and most importantly reused in other projects. The campaign has put in contact many lib authors with people that have reused their code in ways they could not expect. Some other times, users just asked the authors or maintainers for use cases of their code and followed up with an example. Creating community, that’s what all this is about.
When one launches a product or service, one knows they’ll never sleep again 4 hours in a row.
Apocryphal, but probably muttered by our founder Diego Rodríguez-Losada any time during the biicode’s two-year existence.
Especially when your product tries to address a common problem to almost 4 million of C and C++ developers – probably the largest development community by language – that however lacks what in other languages is a basic and a widespread tool: a dependency manager. It is true that several initiatives exist, as RYPPL, Meson, Repobuild, CPMCPP, but unfortunately none of them seem to have a large adoption.
We are proud of where we came from and confident of what we have achieved. We have worked hard to build it, developing and iterating a lot: for example we changed our full codebase from java to python in the process, or rebuilt more than 50% of our codebase in 1,5 months to release v1.0. So we didn’t even consider about making biicode open source. Until today.