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

141–150 of 260 posts

Re: GitUp makes Git painless

#141

Post by swisspol »

menssen wrote: post #135
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)…

Just a thought: I sort of agree with the fact that "pay to use git in a more advanced way" is a bit of a slap in the face to new users. For me, what I absolutely love about this is the quick view of changes in a commit. My usual workflow for this is 1. git log --oneline --graph 2. Copy commit hash to clipboard 3. git show or worse 3. git difftool ^ which is clunky as hell, and made worse that difftool operates on a s…

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

2) free to use but ads or equivalent

3) paid upfront

4) paid with trial

5) paid with in-app purchase for some features

6) a free basic app and a pro app

#1 and #2 are not an option here and #6 is too much overhead and complicates the user proposition.

I don't see how #3 is not worse than #4 and #5. Not an option either anyway: I truly think people should be able to try before they buy for such a product.

#5 is all the trend on mobile and has been demonstrated to work (I've also done that on a couple desktop software and it seems OK). IMO it's the best of both worlds if done right: you get a free useful product as-is, but pay to get even more value of it.

If you think #5 is a "slap in the face of new users", wouldn't #4 also be that? :)

Re: GitUp makes Git painless

#142

Post by baldfat »

sp332 wrote: post #95
zapt02 wrote: post #74

Earlier quoted context omitted.

Yeah, Red Hat is really bleeding money from the all the lost sales caused by CentOS. I can't believe they only made a puny 1.53 billion dollar in revenue last year.. http://investors.redhat.com/financials-statements.cfm

VA Linux Systems set a record for largest IPO and then tanked. The vast majority of Free-software based businesses have tanked too. RedHat is really the exception.

VA Linux Systems was a Hardware Company so your comparison fails in terms of speaking about Free Software Success Stories. Red Hat is far from being an exception. Actually old school closed source software companies are more difficult to start up today in my opinion.

Financial Success Stories abound all around. MySQL, WordPress, Drupal, Mozilla (FireFox), Android, etc.

Re: GitUp makes Git painless

#143

Post by jronald »

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…

Offtopic, but having gone through that recently I found amethyst to have been a great free tiling window manager.

Re: GitUp makes Git painless

#146

Post by Danack »

dcre wrote: post #72

I'm a SourceTree user on Mac. Just tried GitUp out for an hour. Here are the problems I have with SourceTree: * Slow as hell * No/bad keyboard shorts, and setting up custom ones is annoying and buggy * Uses tons of memory — it eventually gets up to 1 GB after running for a day or two, and my repos are not very big. My thoughts on GitUp: * Crazy fast (almost disarmingly so – I think it needs more visual confirmation w…

The slowness appears to be caused by continual directory scanning. For me at least, turning off the "Refresh when files change" option, and so having to do "view, refresh" or Command-R, made SourceTree be zippy again.

And as I'm usually on a laptop, having less continued CPU usage is a good tradeoff against having to press refresh when I'm going to do something in SourceTree.

Re: GitUp makes Git painless

#147

Post by baldfat »

lmz wrote: post #82
dec0dedab0de wrote: post #73

Earlier quoted context omitted.

umm.. Red Hat seems to be doing ok.

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

#148

Post by tokenizerrr »

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.

Just put a samba server on the virtual machine.

Re: GitUp makes Git painless

#149

Post by corysama »

yellowapple wrote: post #84
corysama wrote: post #79

Earlier quoted context omitted.

Please note that the HN community takes a rather strict approach when moderating comments that contribute noise to the conversation. "Nice article!" comments are routinely downvoted. As is sarcasm, witticisms, memes, references and other styles of comments that occur frequently but do not contribute to the discussion. It's a knowingly doomed attempt to hold back the flood of noise that covers Reddit.

The parent comment, however, was actually relevant to the point being discussed (whether or not the ability to fork a free-as-in-speech but not free-as-in-beer program is a significant risk to one's business model). Sarcasm or no, it's a valid point, and thus I feel trying to spout off admonitions in the name of the "HN community" is inappropriate in this context.

Yeah, this was iffy. I totally agree with the comment. But, when it comes to maintaining a community, it doesn't matter if you are right if you are a jerk about it.

For the discussion: I recently paid for the Synergy software KVM even though it is GPL. Synergy's purchase process is very smooth. Paying $10 for the installers was much easier than compiling it myself. And, I was already had confidence that Synergy was useful, good quality, well-maintained software. So, I was happy to support it as long as doing so was convenient.

Re: GitUp makes Git painless

#150

Post by Too »

Touche wrote: post #108
cheald wrote: post #87

It's kind of amusing to me how the pendulum has swung, and we're now producing OS X-only developer software. But then, I'm an oddball who works on Windows as my shell with the real work happening on a headless Linux box via SSH and Samba for 99% of my development.

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.

1. The git integration in visual studio is incomplete (no ssh transport and no log rendering) so you have to complement it with an external tool. 2. Everything in a repo doesn't always belongs to a specific visual studio project.
Post reply on HN