Earlier quoted context omitted.
I'm gonna go out on a limb and say these guys would never have raised if they didn't have "GitHub co-founder" on the first slide of the pitch deck
Ok, that explains everything. Who you know in the Valley is everything. Literally.
We've raised $17M to build what comes after Git
781–785 of 785 posts
Re: We've raised $17M to build what comes after Git
#782Earlier quoted context omitted.
It’s not solved because it’s trash. There’s no good interface for it and people find it difficult to use.
I didn't think Github is that bad but if you think that is the case, why would you give the same guys 17M to try again instead of fix the existing?
Re: We've raised $17M to build what comes after Git
#783> The old model assumed one person, one branch, one terminal, one linear flow. Not only has the problem not been solved well for that old model, it’s now only been compounded with our new AI tools. A bit of a strange thing to say in my book. Git isn't SVN and I think these problems are already solved with git. I agree that the interface is not always very intuitive but Git has the infrastructure which is very much fo…
Re: We've raised $17M to build what comes after Git
#784Earlier quoted context omitted.
No, I’m saying that you can do this without replacing git. You can make it simpler even without replacing git. Aka you just did a strawman, if you are really into these. Also you answered to me in an authoritative way, when even according to you, you don’t understand my comment. You can figure out a logical fallacy name for this. And also of course a nice fallacy fallacy. Btw, I’m also saying that who cannot find how…
> Aka you just did a strawman, That's not what a strawman is. > Also you answered to me in an authoritative way, when even according to you, you don’t understand my comment. No, I didn't understand what referring to production-ready code has anything to do with making mistakes in source control. > And also of course a nice fallacy fallacy. You keep using words you don't understand. > The problem mainly is that when t…
> That's not what a strawman is.
Let’s see Wikipedia.
> A straw man fallacy (sometimes written as strawman) is the informal fallacy of refuting an argument different from the one actually under discussion, while not recognizing or acknowledging the distinction.
Let’s see the relevant part of your comment:
> You're essentially saying we shouldn't improve something because it can be done with a handful of commands
Once again
> an argument different from the one actually under discussion
And once more
> You're essentially saying
So the exact thing for which I used, because I didn’t say that essentially. But luckily for us, you just proved that you intentionally misrepresented my comment, and you intentionally argued against something which is not there. Btw, for which you just proved again that you use fallacy fallacy, and intentionally.
I yet to see a case when somebody says, “you’re essentially saying”, and it’s not strawman.
Let’s move on…
> you don’t understand my comment
And immediately after that, you said that:
> I didn't understand
I know, that from your viewpoint this can be difficult, but maybe, you don’t understand something, because you don’t understand something. Maybe you didn’t understand a single sentence from my original comment, and that’s why you don’t understand even the connections between them. Maybe you didn’t understand the general meaning of my comment, and thus you picked something which your mind cannot comprehend, why it’s there, because you didn’t understand even the basics. You “essentially said” that you didn’t understand my comment in general, by doing a strawman with “essentially saying”, but as you proved it was intentional, so I have no idea about your real thoughts.
It’s possible that the general meaning of my comment is fine, but there is an error in the specifics. Maybe, even the general meaning is problematic. One for sure, we will never know, because you still haven’t asked anything, thus revealing that you don’t even want to know. You proved again btw, that it’s intentional, because you still haven’t attacked its general meaning.
> You're not actually suggesting
As we could see from the definition, this is a strawman. And your first question, so here is the answer: no, and my comment is completely rational regardless of the answer. In other words, if the answer would be yes, my comment rationality wouldn’t have changed even a bit. And since, it’s obvious that the answer is no for everybody, and it’s orthogonal to my comment, thus this is a strawman. The point obviously wasn’t to get an answer.
There are two options at this point:
- your arguments are not in good faith - you do this because you lack skills and/or knowledge
In both cases, any further discussion is pointless.
If it’s the later one, I recommend to learn more, before you ever feel the urge to use any fallacy’s name again. You’re not there yet, but I’m glad that you are interested in avoiding them. A better way of thinking isn’t to avoid specific logical fallacies, but all of them even those which don’t have names. Also using their names won’t ever lead to real discussions in any environments. They can be effectively used only to avoid them for people who cannot think without logical problems as a principle.
If the former, which you proved almost once per sentence, then I hope we will return to positive sum game once, which corrects this behavior with acceptable tools, and you’ll learn from them. Until then, you will continuously make the same mistakes unfortunately, regardless of what I say. I could have proved my points with Lean, and you would still not change a single bit.
Re: We've raised $17M to build what comes after Git
#785Earlier quoted context omitted.
I would argue it being proprietary would be completely unacceptable, for such a position of importance. In any case, Git has become tremendously entrenched over the past couple decades. Anything that hopes to replace it would have to be significantly better to break from the inertia Git has. I’m honestly skeptical as to whether this is even possible in the near future. We’re not at all in the same historical moment a…
yeah, it used to be that things like Perforce could still exist, because when they were created, they could do things that their OSS equivalents could not. but since then, so many people have gotten used to the basic model that git offers (even if they still have issues with details of the syntax). to gain a foothold in this environment is a monumental task, and anything that wasn't unambiguously libre and probably g…