r/learnpython • • Jun 09 '20

Github as a beginner

As a beginner learning python, is it too early to create and start coding simple projects on Github. and how do I transfer these codes (simple calculators) to a website I build subsequently?

401 Upvotes

111 comments sorted by

View all comments

Show parent comments

4

u/thirdegree Jun 10 '20

Re: the rant

So git was definitely not designed to be a beginner tool. What it was designed to be is incredibly powerful and incredibly flexible. And at those things, it succeeds wildly. Git fundamentally trusts it's users (because Linus wrote it for himself, and he trusts himself) and that can end up with a lot of foot shooting.

I teach a course on git, and I'm generally the person that gets asked when nobody else can fix a git issue. And even then, my knowledge of git internals is pretty shallow. But also, I can manipulate changes and change histories to my heart's content, secure in the knowledge that absolutely nothing I can do will lose content (short of manually messing with things in .git/). That's the power of git.

3

u/tradrich Jun 10 '20

The point in my rant is that the _value_ of git doesn't imply the _pain_ of git. The fact that tools like Mercurial exist shows that. It's a pity and disappointing (to me) that it is git that won the implicit marketing battle - I assume mostly due to its association with the Linux Kernel project.
Given its current importance to the world, it's a shame we don't have a better default version control tool. It's sort of too late now because everyone assume that just how it is - that version control management is hard. It doesn't need to be though!

2

u/thrallsius Jun 10 '20

The fact that tools like Mercurial exist shows that.

mercurial exists just because it appeared about the same time as git

but mercurial is almost extinct nowadays compared to git

alternatives like fossil and darcs exist too, and while they don't have such a big market share, they live and prosper

1

u/tradrich Jun 10 '20

I came to Git from Subversion and Perforce. They don't need the technical sophistication of Git since they have central servers - a model that doesn't work with modern open-source driven distributed development.

But really the burden of re-education coming from those to Git - in complex projects - is unwelcome. You want to be able to concentrate on the complexity of your business domain where you have interest and skills and not have to worry *too much* about such things as versioning - as I didn't with Subversion/Perforce.

The delta from these tools to Hg is not too bad - but Git - please - in the heat of production... you don't need that stress!

Proponents of git - indeed it seems they're often enthusiasts - don't broach any criticism of the tool and tend to blame the user. I cite the wide interface - the profusion of keywords and symbols, the lack of coherence between them to say that "git could do better!" for the user (without any sacrifice of functionality).