Is there anyone interested in doing a group where we learn to code together? Using mostly free resources? And work on a common project, perhaps? Programming language is open for discussion.
#practicecoding
Gibt es Menschen die Interesse hätten an einer Gruppe, in der wir Programmieren lernen? Dabei v.a. freie Ressourcen nutzen? Und vll. an einem gemeinsamen projekt arbeiten? Programmiersprache ist noch offen. #practicecoding
@TQ If you decide to go with Python, I could help out if you have questions. Same goes if you run into trouble using git, this is something I teach people on a regular basis :)
@rixx @TQ This might be helpful, too: http://ohshitgit.com/ (website titled: "Oh shit, git!")
@ginsterbusch @rixx Ah, sorry, was unclear. I meant either GitLab or GitHub. These provide additional options.
@TQ @ginsterbusch I really enjoy using GitLab. They provide new features every months, are easily self-hosted and provide some things GitHub doesn't.
@rixx @ginsterbusch GitLab was mentioned by so. before.
@ginsterbusch Ah, you aren't really interested in constructive dialogue, are you? Just tool bashing and stuff? Carry on then, that's not my kinda thing.
@ginsterbusch @TQ It doesn't have a graphical UI, but even a command line interface is a user interface, and git's is fairly nasty due to lots of magic parameters and inconsistencies . I love using git, I love its data structure, but its UI is still horrible.
@rixx @TQ my guess is, you havent been around much. there is lots of tools, apps, utils etc. pp. around with WAY worse syntax. just take ffmpeg / avconv or grep or ls or tar or most of the gnu utils .. $younameit :)
I always havs to look up stuff, but then, that counts for the rest as well, so I'd rather call it "in true unix cli spirit" than anything else :D
First off, I think "you haven't been around much" is a terrible argument to make, because less experience does not discount opinion.
Secondly, I *have* been around much, and I know that ls and tar and the fuckups that are fdisk &co have horrible interfaces, too. I just do not think that that's a good excuse to build bad user interfaces, especially if you start off after the 90s. I still use and like git, but bad UI should be called out.
@rixx @TQ thats what you said. I could have said: look over the tellerrand, there is much worse. or just a really derogative "you know nothing, puny mortal". but i chose that phrase as a middle way. and really: there is worse. much worse. the only thing that is truly bad is: there is no reliable cross platform GUI (or just TUI) git tool / wrapper. sorrowfully remembering TortoiseSVN .. that was a fun tool to use :'(
@ginsterbusch @rixx @TQ no ncurses. But the tig command is very nice. :D
@rixx @TQ
I don't agree that the user interface is horrible (it was in earlier versions though 😉). I think many commands or options just only make sense after understanding some of the internals of Git. For example that the ID of a commit changes during rebase makes perfect sense, yet it is very confusing in the beginning (or so it was for me).
Also, @TQ, feel free to ask me questions about Git if you have any. I often get the impression that I'm still far from expert but at least I have been using Git for almost 10 years now. 😄
@TQ @winniehell oh no, Git is already 10 years old? we'll have to move to something new soon!
@TQ Git has a horrible, horrible user interface - everybody runs into lots of problems at first. If you learn well with interactive tools, try https://try.github.io/levels/1/challenges/1 , if you learn well from text, try chapters 1.3 and 2 of https://git-scm.com/book/en/v2/Getting-Started-Git-Basics … I don't learn well from videos so I have no recommendation there, but visualizing git concepts can be very very very useful!