4 ms·
> Unfortunately, even now, it seems that there is a lot catching up to BK still to be done. To be fair, we had kernel level programmers working on it, we don't
by ymbeld 6y ago
> Unfortunately, even now, it seems that there is a lot catching up to BK still to be done. To be fair, we had kernel level programmers working on it, we don't think anyone will pick up our code, you pretty much have to be a top 1-2% programmer to work on it, it's all in very disciplined C, people don't seem to like that any more.
Oh my oh my.
- luckydude 6y agoBelieve me, I would do backflips if someone wanted the BK source base, it's got almost 2 decades of my work in it, north of 140 man years. It's a lot to just let fade away. But I assembled a team of people better and smarter than me, I did my best to keep the code simple but I didn't always succeed. If you, or anyone, wants to pick it up, I'm happy to answer questions.
- mucholove 6y agoWill take a look at it. At this point, the trick to creating a sizable git alternative I think is to Trojan horse coding into a new realm with “no-code” like apps. One of my favorites is Fossil by Richard Hipp. I wonder what your thoughts on it are. I think it is RCS, but usability wise I think it’s way ahead of git. I just recently learned C and I really like the coding style Hipp uses as well. :)
- luckydude 6y agoRichard is awesome. He also did sqlite. As for Fossil, I'm a fan of his UI and code, but haven't looked in detail at the design. I'm pretty sure it is patch based with everything stored in sqlite. It's an OK way of doing things but not if you understand a weave. But no disrespect intended towards Richard, I've met him plenty of times and enjoyed it each time. Great guy.