GitUp makes Git painless
211–220 of 260 posts
Re: GitUp makes Git painless
#212Earlier quoted context omitted.
Maybe I'm odd but apart from working in VS, none of your statements hold true for me. I saw this and was like 'gimme gimme' only to find out it is OSX only. Quite a disappointment, especially given the recent stall (afaik) in SourceTree for Windows development, making me go back to the command line more and more again. I vastly prefer standalone tools for things like git because else I have to learn the builtin tools…
Why exactly do you stick with Windows? Hardware?
1) Hardware - cost is 1/2 Mac hardware, and I can upgrade cheaper as well. For example, my ultralight notebook came with 4GB Ram and a 128GB SSD. For ~$1000 - Mac equivalent was ~$1400 at the time, with no option to match the screen (1080p). Since then, I've upgraded but the SSD and Ram for another $300 - would have cost almost $700 to do the equivalent upgrade on the Mac and it would have been at the time of purchase.
2) I've grown up using Windows, CMD, batch files, etc. I know my way (a little) around the registry, services, etc. I'd have to relearn all of that on the Mac.
3) I hate all the program menus being at the top of the screen. I have a Mac on my desk at work...and it just drives me nuts. I'm sure I'd adapt, but it bugs me.
I could find more, but I've come to admit that I'm just a Windows user. If I need Linux or something, I just install a VM and go to town.
Re: GitUp makes Git painless
#213Awesome. Now 13% of people that would like to use it can [0]. Cool idea. Just wish it wasn't tied to Mac. 0 - http://en.wikipedia.org/wiki/Usage_share_of_operating_system...
http://stackoverflow.com/research/developer-survey-2015 If StackOverflow surveys are any indication, more like 21.5%. I completely agree that I wish it wasn't tied to Mac (Linux please and thank you), but the proportion of developers is higher on OS X than in the consumer market. I have no data to support this, but I suspect that many of those devs on Mac are also front-end, which (again, no data) makes me think that…
Re: GitUp makes Git painless
#214I realize this is a pretty broad question, but what is it about Git that people find painful ? Could be Stockholm Syndrome on my part, but I have a pretty hard time understanding why someone can't spend a week getting up to speed with a tool they intend to use for years to come.
Yeah, I was coming here to post that Git is already painless. It's a tool you are intimately using if you're doing anything other than Hello World projects with your team; it doesn't seem too much to ask to actually learn how it works. And once you know it's painless. Edit: I was thinking about it a bit more and it's actually one of the least painful tools I have ever used on a computer...
Re: GitUp makes Git painless
#215Earlier quoted context omitted.
How do you resolve 'executable' files in your VM? I've not been able to run node apps because executables end up getting stored in /node_modules/, but if that is on a windows share, no executable flag is stored. Resolving the FS differences has always been the biggest pain for me using windows as the core OS.
The node ecosystem in general is a mess; I don't think you can blame that on the OS. I did a node project recently and I've still not been able to get it to run on two seemingly identical systems in the same way.
Are you using npm shrinkwrap?
Re: GitUp makes Git painless
#216Earlier quoted context omitted.
Could someone comment on the main complications on developing something like this for both Mac and Linux? From my point of view, they is so much common ground, comparing to a Mac/Windows support, that I'd strive for an application to cover both! And that's not something that you could always decide after launching the first time, you need to have it in consideration during design...
The non-UI layer can be made 100% portable for sure (although in the GitUp case it's not really since I chose to write it in Obj-C for productivity reasons). The UI layer is absolutely not portable: it's all low-level CoreGraphics code for the rendering, some CoreAnimation, and a ton of AppKit of course. You could have a version written in a cross-platform UI toolkit or Java or what have you, but you could not possib…
Re: GitUp makes Git painless
#217Earlier quoted context omitted.
…and not release under a free/open license for GNU/Linux. Yeah, right. That stinks. No joke. Proprietary software for proprietary OS's ought to not exist.
2015, the year of the GNU/Linux desktop! For real now!
Re: GitUp makes Git painless
#218Earlier quoted context omitted.
Red Hat does OK because they can sell support for an OS to enterprises. Selling support for a Git GUI to individual developers (even end user apps in general) is a bit harder.
Please look at mobaxterm's model for an example. GPL licence [ http://mobaxterm.mobatek.net/download.html ]
For a single app: take a look at what happened when XChat tried to sell their Windows binaries as shareware: http://en.wikipedia.org/wiki/XChat#Licensing
Re: GitUp makes Git painless
#219Earlier quoted context omitted.
Red Hat does OK because they can sell support for an OS to enterprises. Selling support for a Git GUI to individual developers (even end user apps in general) is a bit harder.
Please look at mobaxterm's model for an example. GPL licence [ http://mobaxterm.mobatek.net/download.html ]
Re: GitUp makes Git painless
#220There's something really satisfying about seeing a visual representation of my git repositories, but my overall impression is that I'm not going to get any productivity gains here. If you know what you're doing, CLI is just faster. I understand that it's aimed at more novice developers, but I think for those developers it's even more important to use the command line. Developers that get into the habit of using unnec…
It's not as snazzy as in the article but this alias in my .gitconfig is an integral part of my git workflow: gr = !git \ --no-pager \ log -n 16 --graph --date-order --date=short --branches \ --pretty=\ '%C(yellow bold)%h%Creset\ %Creset %C(blue bold)%d%Creset\ %C(white bold blink)%s' The 'gr' is short for 'graph'. You can tweak the -n to show more history. I actually have several of these, 'gr', 'grr', 'grrr', etc. t…