I don't open source my code bc I don't understand git
So, you don't "git it"?
I'll escort myself out.
Git push yourself out* to make the obvious joke
We are the same
git good
it's just linked lists of commits (except when merging)
I don't understand linked lists
In internet terms: It's just a soyjak holding a box with data who is pointing at another soyjak holding a box with data who is pointing at another {insert N-3 of the same soyjaks} soyjak with a box with data without an arm to point with
I don't understand what a soyjak is.
Kourtesy of Krita
I still don't understand Git but I like this image
each commit points to the one before. additionally a commit stores which lines in which files changed compared to the previous commit. a branch points to a particular commit.
There's a guy out there who made a reversible NES emulator, meaning it can run games backwards and come to the correct state. He made a brilliant post on Reddit /r/programming linking his ideas for the emulator to quantum mechanics.
Then he was asked why he didn't distribute his program in git. He said that he didn't know git.
To me, that's a pretty good example of the difference between computer science and software engineering.
You can open source your code just by uploading it on some kind of cloud storage and setting it as publicly available.
I don't open source my code bc I don't understand git
So, you don't "git it"?
I'll escort myself out.
Git push yourself out* to make the obvious joke
We are the same
git goodit's just linked lists of commits (except when merging)
I don't understand linked lists
In internet terms: It's just a soyjak holding a box with data who is pointing at another soyjak holding a box with data who is pointing at another {insert N-3 of the same soyjaks} soyjak with a box with data without an arm to point with
I don't understand what a soyjak is.
Kourtesy of Krita
I still don't understand Git but I like this image
each commit points to the one before. additionally a commit stores which lines in which files changed compared to the previous commit. a branch points to a particular commit.
It's just a thingie
Almost... To be precise it's a Merkle DAG
It's perfectly fine to just make a zip available
Branchophobic
There's a guy out there who made a reversible NES emulator, meaning it can run games backwards and come to the correct state. He made a brilliant post on Reddit /r/programming linking his ideas for the emulator to quantum mechanics.
Then he was asked why he didn't distribute his program in git. He said that he didn't know git.
To me, that's a pretty good example of the difference between computer science and software engineering.
You can open source your code just by uploading it on some kind of cloud storage and setting it as publicly available.