|
|
|
|
|
by alphapapa
3780 days ago
|
|
I don't want to pooh-pooh anyone's hard work--please don't misunderstand me--but I am legitimately curious: why put so much effort into building a house of cards upon a foundation of shifting sand? Your project is completely dependent on GitHub's reliability, integrity, and goodwill. It could implement its own version of your enhancements and render yours obsolete. Arguably, it should do that, because what's the point of relegating useful enhancements to third-party products? So doesn't that mean that your project is living on borrowed time? Why not build upon an open platform instead, one that you can control, one that can't be ripped out from under you? Again, I don't mean this as criticism, I'm just very curious, because I don't understand. |
|
- There is the front end which is 100% JavaScript and this is important since it allows me to build on top of existing web solutions like GitHub
- There is the indexing engine which was insanely hard to develop and is what makes my solution unique.
I've attached some screenshots that shows how I'm using my JavaScript technology to integrate with Bitbucket here:
http://imgur.com/a/7AME6
I've also uploaded some screenshots that shows how I monitor/manage indexing. Right now, my indexing engine can easily process 10s of thousands of repositories with millions of branches on a single machine. The indexers are designed to scale horizontally and developing them was insanely hard and that's what I'm really selling. There is a reason why GitHub stopped indexing commits a few years ago. And why Bitbucket has a 5 year old ticket about code searching:
https://bitbucket.org/site/master/issues/2874/ability-to-sea...
Should the worst happen and I get shut out by GitHub and Atlassian, there is always GitLab, Gogs, etc. For now, I'm more than happy to build on top of GitHub and ensuring my solution works with their Enterprise offering.