Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitUp makes Git painless

gitup.co

Post reply on HN
Print view View original

171–180 of 260 posts

Re: GitUp makes Git painless

#171

Post by EC1 »

hatsix wrote: post #83
jakobegger wrote: post #54

Earlier quoted context omitted.

The Mac is a phenomenal platform to launch right now if you make software targeted at developers. There's huge growth in mobile development, and many mobile developers work on OS X. Not just iOS developers, I'm seeing lots of Android devlopers working on Macs too recently. And if you make a new tool, you should go where the young (in the sense of experience, not age) developers are. Experienced developers already hav…

Having just (involuntarily) switched to a Mac at work, I can also attest to the fact that Mac users tend towards impulse buying software... The fact that I have to buy software to get proper window management and a good window switcher makes me furious. App-only switching makes no sense to me. I just want to pull up the last window I was looking at, I don't want to have to think about whether it was in the current ap…

>Most people in the office have spent $100 on software that just customizes the OS, not even considering the other dev tools that they purchase.

What's your point? Most people have spent >$100 on going to a theater to watch movies, which is arguably a much worse way to spend money than improve your workflow.

Windows has much worse window management than OS X, and so does Linux. Just because the info is there, doesn't mean the Apple team should handle ever edge case and scenario ever.. that's why you have applications. Should an OS also come with a perfect and free IDE?

Re: GitUp makes Git painless

#172

Post by Macuyiko »

shadowwolf007 wrote: post #164
Touche wrote: post #108

Earlier quoted context omitted.

There's no market for this sort of thing on Windows. The vast majority of development that happens on Windows takes place in either Visual Studio or Eclipse, and those developers prefer tools that integrate with their IDE rather than be standalone.

We use git exclusively as a Windows-based shop and only 1 person uses the git integration with Visual Studio. Everyone else uses different solutions from tortoise to source tree to command line. I think there's definitely a decent market for this sort of thing - I've had plenty of conversations locally that end with "Wow, I'm so glad to get away from Visual Studio for this"

Meh, same here, some are using git bash on top of cmder, some are using Git Gui, some integrated with Eclipse, some integrated with Rstudio.

Re: GitUp makes Git painless

#173

Post by zatkin »

scotthew1 wrote: post #89
zatkin wrote: post #56

> http://gitup.co/images/speed.png I hope no-one here ever has to deal with a tree like this.

i'd expect any significant project to have a tree _at least_ that complex. here's a small sample of my company's tree with several team repos merging into a master repo. this tool really loses its usefulness quickly for repos this complex.. http://i.imgur.com/xl2a1ac.png

Are you on the art industry?

Re: GitUp makes Git painless

#174

Post by swisspol »

menssen wrote: post #163
swisspol wrote: post #141

Earlier quoted context omitted.

Thanks for the kind feedback! > So my suggestion is: remove ALL the modification features from the free version, release it as a separate app called "GitUp Viewer" or something, and then sell the version that is actually a git client. Hmmm... but wouldn't that be exactly the same problem of "slapping users in the face", except now with 2 apps? There aren't that many options to distribute desktop software: 1) freeware…

Here's a specific scenario: I work at an organization with a lot of developers who first learned to use git through SourceTree. As far as they are concerned, "what SourceTree can do" is the entirety of how git works. While this is probably not great overall, I do think it is the experience of a lot of newer git users or people who aren't used to a CLI. I also work at an organization where it is difficult (mostly just…

Got it! Thanks for the detailed explanation.

Re: GitUp makes Git painless

#175

Post by alexchamberlain »

hatsix wrote: post #118
alexchamberlain wrote: post #96

Earlier quoted context omitted.

+1 I was going to make a rather sarcastic comment that this is for "professional engineers", but is OS X only. Ubuntu on a VirtualBox on Windows for me.

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.

I spend a lot of time editing files via sshfs, and running builds on remote servers.

Re: GitUp makes Git painless

#176

Post by depr »

dan00 wrote: post #5

I don't know if it's such a good idea to start by showing how easy changing commit messages is or even have this option that easily available, because after all you're changing the history and the beginner might not be aware what this really means, and beginners seem to be the target audience for this tool.

That part is actually what made me excited.

Re: GitUp makes Git painless

#177

Post by bau5 »

quadrangle wrote: post #10

Git is a registered trademark, I don't see notice of permission… maybe they didn't ask and might not have it?

You can email the Software Freedom Conservancy to report its use, even if you don't know whether they have permission or not. They'll sort it out. http://git-scm.com/trademark

Also I have the feeling that if they had permission that they wouldn't forget to add a notice about it to the bottom of their page.

Re: GitUp makes Git painless

#178

Post by recursive »

swisspol wrote: post #8
dan00 wrote: post #5

I don't know if it's such a good idea to start by showing how easy changing commit messages is or even have this option that easily available, because after all you're changing the history and the beginner might not be aware what this really means, and beginners seem to be the target audience for this tool.

Actually, GitUp was designed to be for professional software engineers first, even though it may also appeal to beginners. It's faster than the CLI for a number of operations, and offers features that don’t even exist natively in Git like a visual commit splitter or a unified reflog browser. The Map view documentation does have a large warning on rewriting history (which obviously is required for a number of operatio…

Professional software engineers can also be git beginners.

Re: GitUp makes Git painless

#179

Post by MichaelGG »

baldfat wrote: post #50
swisspol wrote: post #31

Earlier quoted context omitted.

Anything can happen (I have a number of projects that are open-source, some other close-source), but the idea so far is to have a free app with an in-app purchase to unlock the advanced/pro feature. I might make open-source some of the "Git toolkit" I built for this app, but it's too early to say. The reason for expiring builds is that 1) it's pre-release, 2) it's a software intended for professional engineers and 3)…

You don't need to make an application closed source to have in app purchases. Look at mobaxterm [ http://mobaxterm.mobatek.net/license.html ] It is licensed under GPL version 3. It has a free version and a professional version which cost $69 per user. This does not break the GPL. You may already know this but it seems like a lot of developers think open source mean Free as in cost. [ http://www.gnu.org/philosophy/sel…

Wait, so I just bought MobaXterm (it's awesome just wish the UI was cleaner and faster) - I can go hand out copies to anyone I wish, legally?

I don't want to do that, cause I'd prefer they get more money, but it's neat to know. (I'll double check the license of course.)

Re: GitUp makes Git painless

#180

Post by graffitici »

loumf wrote: post #62
swisspol wrote: post #11

Earlier quoted context omitted.

You get the usual Git error "unable to fast-forward" which means in plain English that what's on the remote repo doesn't match what you have locally anymore, so you can't push, unless you force. In such cases, GitUp just prompts you if you want to force push. If you decide to force push, then your updated commit message is on the remote repo as well. This is completely safe if this is your private repo, or you are pu…

Which makes it really weird that your video shows you doing this to master, a branch very likely to be shared.

I agree. Instead of promoting this as something very simple to do with GitUp, we should stop people from having people the urge to change commit messages.

Plus, as even programming data structures are increasingly immutable, I don't see why I would go change the commit message from a week ago.

Post reply on HN