So far, the candle is not worth the match. I can and do easily accomplish plenty well enough the functionality you mention now for just one user, me -- I'm a sole, solo founder. And there is the intellectual property security issue, for a code repository or the cloud, and so far I don't use or really need either. I have lots of good uses for my time and have to allocate carefully.
Similarly, while I'm developing on Windows with no use of Linux at all, I make no use of Visual Studio; I greatly prefer my favorite text editor KEdit and its macro language Kexx, essentially Rexx.
I'm not saying that others should do what I'm doing. By far my favorite tools are KEdit and Rexx. Next comes D. Knuth's TeX.
I accept that if I had 50+ software developers then they would likely be heavy users of Visual Studio and GitHub. But for me, for now, they aren't worth the botheration.
Botheration, mud wrestling with software, has, after poor documentation, been my biggest obstacle.
ALL the work unique to my project has been fast, fun, and easy, the idea, applied math, code, etc. Thus I have a real sore spot about new, external tools -- my experience with such external things has been botheration I call mud wrestling. The time wasted has not been hours, days, or weeks but far beyond that.
IMHO the biggest bottleneck now in the future of computing is poor documentation. Second is mud wrestling with new products including tools.
The code is 100 K lines of typing but about 25,000 programming language statements, that is, 25 KLOC. That is, there are a LOT of comments and links to documentation in the code.
Similarly, while I'm developing on Windows with no use of Linux at all, I make no use of Visual Studio; I greatly prefer my favorite text editor KEdit and its macro language Kexx, essentially Rexx.
I'm not saying that others should do what I'm doing. By far my favorite tools are KEdit and Rexx. Next comes D. Knuth's TeX.
I accept that if I had 50+ software developers then they would likely be heavy users of Visual Studio and GitHub. But for me, for now, they aren't worth the botheration.
Botheration, mud wrestling with software, has, after poor documentation, been my biggest obstacle.
ALL the work unique to my project has been fast, fun, and easy, the idea, applied math, code, etc. Thus I have a real sore spot about new, external tools -- my experience with such external things has been botheration I call mud wrestling. The time wasted has not been hours, days, or weeks but far beyond that.
IMHO the biggest bottleneck now in the future of computing is poor documentation. Second is mud wrestling with new products including tools.
The code is 100 K lines of typing but about 25,000 programming language statements, that is, 25 KLOC. That is, there are a LOT of comments and links to documentation in the code.