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

61–70 of 260 posts

Re: GitUp makes Git painless

#61

Post by swisspol »

oldmanjay wrote: post #44
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)…

What made you decide where the line is for "advanced" features? It seems like doing any sort of actual work is considered advanced. There isn't a feature I can think of that would make me consider paying for development tools, so I'll never be buying your software, so feel free to tailor your response (if any) with that in mind.

Fair question. It's not decided yet. The easiest code-wise was to put the Map editing features in that bucket, so that's what I did for now. Everything else (browsing, committing, stashes, repo config, undo / redo, cloning...) is free and no registration needed.

Re: GitUp makes Git painless

#62

Post by loumf »

swisspol wrote: post #11
graffitici wrote: post #7

Earlier quoted context omitted.

I agree. If you've already pushed to other repos with the old commit message, this can cause issues. The only time I actually change the commit message is when I'm sure that nobody else has seen it. I'm not even sure what happens when you change the local commit message, and push it again. Does it just get updated in the remote repo?

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.

Re: GitUp makes Git painless

#63

Post by dikaiosune »

aagha wrote: post #59

Awesome. 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 they might care a lot more about a nice GUI tool than devs on other OSes.

Re: GitUp makes Git painless

#65

Post by cookiecaper »

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…

Although the GPL allows authors to charge for software, it disposes of all legal copyright protections that make such charges practical. Charging for GPL software doesn't mean anyone will pay you, it just means that everyone will get the free builds from someone else, which is even less desirable than releasing free builds since you lose control of distribution. Look at Red Hat and CentOS for case in point.

Re: GitUp makes Git painless

#66

Post by okal »

I 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.

Re: GitUp makes Git painless

#67

Post by bcg1 »

Proprietary development tools are a trap. And this software is just a proprietary wrapper around a real community product. Doesn't matter if you rewrote the library for interacting with the database... standing on the shoulders of giants.

Are we really at the point where "professional engineers" need to buy a GUI as a substitute for a fast, extensible, cross-platform command line tool that is so easy to use that even I could figure it out?

Re: GitUp makes Git painless

#68

Post by FooBarWidget »

bcg1 wrote: post #67

Proprietary development tools are a trap. And this software is just a proprietary wrapper around a real community product. Doesn't matter if you rewrote the library for interacting with the database... standing on the shoulders of giants. Are we really at the point where "professional engineers" need to buy a GUI as a substitute for a fast, extensible, cross-platform command line tool that is so easy to use that even…

So you say, but if that's what everyone thought then GPL would have won instead of MIT. In every thread, the amount of "GPL is viral" people far outnumber the GPL defenders. It's clear that most people prefer to be able to build proprietary tools on top of open source ones.

Re: GitUp makes Git painless

#69

Post by tluyben2 »

okal wrote: post #66

I 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...

Post reply on HN