141–150 of 248 posts
Please, please don't name your installer 'setup.exe' When I browse to my downloads folder, the most frustrating thing in the world is trying to figure out where 'setup.exe' came from.
I think it's called that way because of some kind of naming convention that Windows expects from installers?
Great news. I got flamed a month ago [1] for noting how difficult it is to get up and running on GitHub in the Windows world, where things like generating SSH keys aren't exactly part of the daily routine. Glad to hear that they were listening. [1] http://news.ycombinator.com/item?id=3871699
The ssh setup is a barrier to entry for a great deal of Windows users, simply because they don't have to deal with such things on a daily basis. Whether they all should know these things is debatable.
I personally couldn't give shit how 'it' works, as long as I don't have to waste my precious time having to learn something I don't need to. I don't want to have to learn machine code for the same reason. We abstract to become more productive. We build on the shoulders of giants. We don't re-invent the wheel. I could go on...
The bottom line is that the previous installation for Windows was manageable, but still it was a drag. Luckily there were enough good resources on the web to help you through it. However, it was time consuming and that barrier has now been removed.
In my opinion that's great. It follows Dieter Rams' principles of good design, namely:
Good design is as little design as possible. Less, but better – because it concentrates on the essential aspects, and the products are not burdened with non-essentials.
http://www.vitsoe.com/en/gb/about/dieterrams/gooddesign
Let's remember that Git is a distributed source control mechanism. It needs to move versioned code around. That is its pure purpose. When the security setup takes more effort than the source control you're doing it wrong.
That being said, the common language of the Git world will remain the command line. The vast majority of examples you will find on the web when you are learning how to use Git will be executed via the command line. That fact in itself means that you should still learn the basic commands and get familiar with git bash.
EDIT: I hope this gives a fairly balanced opinion from a typical Windows Git user. I appreciate that this topic is a heated one.
Earlier quoted context omitted.
Nobody in this thread implied that you are flaming, nor intended to insult you; the person you are responding to is not the person you originally responded to, and he is commenting about people in other threads flaming him. I resent having to explain this to you. What the hell are you so angry about, seriously? People have less expertise than you, and that makes you upset?
>I resent being flamed because I don't fully understand the subtleties of zsh or nginx or or whatever other shiny toy someone else happens to find essential knowledge. Your world might not necessarily be mine. That was in the post I replied to. It's insulting because it's accusing me of things that I didn't do. I merely am just a bit floored by the notion that following these instructions, http://help.github.com/win-…
Earlier quoted context omitted.
>I resent being flamed because I don't fully understand the subtleties of zsh or nginx or or whatever other shiny toy someone else happens to find essential knowledge. Your world might not necessarily be mine. That was in the post I replied to. It's insulting because it's accusing me of things that I didn't do. I merely am just a bit floored by the notion that following these instructions, http://help.github.com/win-…
I'll repeat this: he was saying other people flame him in those situations, not you.
Earlier quoted context omitted.
You can't follow 3 step-by-step instructions, insult me by implying I'm flaming and then drudge up completely unrelated tools in a discussion about ssh-keygen? What do you people want? Seriously? Yes, I'd love to have a big red easy button. It could autoconfigure MySQL, and write init scripts, configure deploy environments because apache conf files are too complicated to learn. Hell, it could even write my backend co…
Nobody in this thread implied that you are flaming, nor intended to insult you; the person you are responding to is not the person you originally responded to, and he is commenting about people in other threads flaming him. I resent having to explain this to you. What the hell are you so angry about, seriously? People have less expertise than you, and that makes you upset?
So to all of you that actually know the difference between merge and rebase and what the difference between origin and local branches are :hattip:
Please, please don't name your installer 'setup.exe' When I browse to my downloads folder, the most frustrating thing in the world is trying to figure out where 'setup.exe' came from.
I think it's called that way because of some kind of naming convention that Windows expects from installers?
Earlier quoted context omitted.
You're being down-voted into oblivion. You get even more insulting as you're falling down in your edit. Mm disclaimer: I'm a windows dev by day. I introduced git into that shop I'm working at, the rogue 'I set it up, would you technical guys like to work with it' way. This happened 1.5 years earlier, today it's the blessed and only source control in play (ignoring one sad division having to deal with tfs.. Oh the ago…
"You want to use Git, you should know how to use Git" If that's insulting, then I'm going to have to learn to live with being a cruel, mean person. Also, it's GitHub's fault that they use an existing secure method of transferring source code instead of writing a new protocol that's easier for you to use. Because 4 step-by-step instructions are too hard to follow. OK. I'm not even asking that you understand it, but si…
"Also, it's GitHub's fault that they use an existing secure method of transferring source code instead of writing a new protocol that's easier for you to use. Because 4 step-by-step instructions are too hard to follow. OK."
"I'm not even asking that you understand it, but simply be able to follow very, very simple instructions."
"If you're a dev, source control is one of your tools. Learn it or find a tool that holds your hand more. I don't know how it gets more hand-holdy than step by step instructions that take 4 minutes to carry out."
For those of you looking for a nice Git client for Windows, I suggest checking out TortoiseGit[1]. I can't recommend it enough. It is such a powerful peace of software and I am surprised it is not brought up in discussions more often. http://code.google.com/p/tortoisegit/
I use TortoiseGit (and was a long time user of TortoiseSVN before that), but I find it to be a poor substitute for the command line. I feel like they tried to make the names of git commands more user friendly, but having already grown accustomed to misnomers like "git checkout" it often takes me a little while to find the right action in TortoiseGit.
Earlier quoted context omitted.
PKI has nothing to do with SSH keys. Github's use of SSH does not use certificates, and github has no certification infrastructure.
My apologies, I abuse "PKI" to mean "PK infrastructure" (which I know is what the acronym stands for, I'm making a bit of tongue-in-cheek commentary), I think it's silly that PKI implicitly means CAs but according to Wikipedia at least, you're correct.
Everything you've said in this thread has been bang-on, and the replies you're getting are deeply depressing.
Earlier quoted context omitted.
"You want to use Git, you should know how to use Git" If that's insulting, then I'm going to have to learn to live with being a cruel, mean person. Also, it's GitHub's fault that they use an existing secure method of transferring source code instead of writing a new protocol that's easier for you to use. Because 4 step-by-step instructions are too hard to follow. OK. I'm not even asking that you understand it, but si…
The insulting and derogatory remarks is stuff like: "Also, it's GitHub's fault that they use an existing secure method of transferring source code instead of writing a new protocol that's easier for you to use. Because 4 step-by-step instructions are too hard to follow. OK." "I'm not even asking that you understand it, but simply be able to follow very, very simple instructions." "If you're a dev, source control is o…