181–190 of 248 posts
I'm interested to see how the community responds to their choice of ClickOnce as the deployment method. I use ClickOnce for several of my applications, and I'd say the users who dislike it the most have the highest technical aptitude (which, I'd guess, is a large part of GitHub's user base).
Earlier quoted context omitted.
Interesting. What's the usual cause for complaint?
The most common questions/complaints I get are: - Why can't I find the installation directory? (ClickOnce doesn't use the standard C:/Program Files/ location, it stores program files in C:/Users/ /AppData/Local/Apps/2.0 for security reasons.) - Why does the installer need a network connection? (ClickOnce downloads the required setup files from the internet.) The lack of a standard Program Files/.exe deployment also m…
Earlier quoted context omitted.
To be fair, the GitHub for Windows UI looks a lot like the Zune UI, which has been around for a while now. I've not been able to try it yet on my Windows machines, but the screens I've seen look like they borrowed heavily from what Zune had.
GitHub for Mac borrows from a lot of good Mac UIs, and it looks like GitHub for Windows does the same from good Windows UIs. Frankly I find this refreshing. I'm tired of applications that build their own interaction layer and then implement that across every platform regardless of that platform's idioms. Or, even worse: Air apps.
Earlier quoted context omitted.
I apologise. My comment was only modestly related to it's context. I've been suffering from a bit of *nix-fatigue at the moment and I wanted to vent.
From looking at the desktops of an ordinary office, it may be difficult to realize that, when you are talking about internet connected servers, it's a very *nix world. One of the reasons why I recommend using Linux on the desktop if you develop software for anything non-Windows: it's handy to have more exposure to the environment your code will run on. If you run Eclipse to develop Java code that'll run under Tomcat…
Earlier quoted context omitted.
"Scary crypto stuff"? So you don't understand how PKI works and you're trying to use distributed source control? (I say this not to be a jerk, but because there aren't exactly a wealth of good alternatives given it is a distributed source control mechanism. PKI comes with the territory and an SSH key generation is part of that) GitHub doesn't take any more setup than a standard Git setup takes (well, outside of signi…
I get really sick of this attitude. None of us want to understand every single domain of knowledge from set theory or quantum physics up to cosmology or social psychology. I personally have been forced to learn more low-level Unixy things than I ever wanted to. I want to write simple and elegant front and back end code quickly so I can spend my spare time honing UX and other human-facing aspects of my work. I resent…
Earlier quoted context omitted.
It's not about being unfamiliar with the CLI, it's that Windows isn't like OSX/Linux in that you can just store your keys in a .ssh folder and be done with it (at least not if you don't use cygwin/msys) The method I chose in Windows was to use pageant (part of Putty) to load the keys. Not sure if I missed this option but you can't autoload keys so when you restart pageant you have to readd the keys (which is not terr…
> Windows isn't like OSX/Linux in that you can just store your keys in a .ssh folder and be done with it (at least not if you don't use cygwin/msys) Then, by all means, use Cygwin or anything that helps you, even if it doesn't come with Windows, if it isn't provided by Microsoft, doesn't look familiar and if it doesn't play well with Visual Studio. If you code for Windows you are coding against an insanely complicate…
Compare this with Mercurial, which runs great from the command line on multiple platforms. I actually prefer the command line for SCM work, but git makes it hard.
Earlier quoted context omitted.
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…
It's not insulting to point out that the instructions are very simple, easy to follow, and easy to understand. Everyone here is smart enough to understand these things, and it's utterly bewildering that they angrily refuse to spend 5 minutes learning about something new in order to use something new.
Let's imagine a company creates some form of hardware widget that requires some form of setup before it can be used. Initially the setup involves four steps that the company feels is "simple". Now, let's say a number of their customers have trouble with those simple instructions for different reasons. What's the proper response from that company?
A: Maybe we should think over the instructions to identify some problem spots as to why people are having trouble? Maybe we should ask some of these people what part are they having trouble with? Maybe we should consider a more in-depth explanation to people who have never used a similar device before?
B: If people aren't smart enough to figure out our simple instructions then they're too stupid to use our product. We could just ignore them but instead we'll insult them because they just don't get it. After all, if they're in our industry then they should already know how to do this.
I'm not saying that everyone should use response A, since most likely the problem has been answered somewhere. But too many people go with response B with absolutely no benefit to anyone in any way.
Earlier quoted context omitted.
Checkout in SVN does not mean the same as it does in git. SVN Checkout is more like Git Clone. Checkout in git means change to a different branch. You "checkout a branch" in git. I think it is better for TortoiseGit to match the semantics of git rather than match the semantics of TortoiseSVN. It causes some confusion coming from SVN for sure, but once you start using git, you should learn its dialect. It would be wor…
That was my point. For example, TortoiseGit presents "revert" instead of "checkout" (e.g. on a file, not a branch). "revert" in git actually means something else entirely.
Earlier quoted context omitted.
There are several, they just don't get much attention these days.
Do you have a list or such? I'd love to use these. I've only seen MetroTwit, Zune, and this.
That's one I stumbled upon a while back.