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

241–250 of 260 posts

Re: GitUp makes Git painless

#241

Post by X-Istence »

reitanqild wrote: post #186
X-Istence wrote: post #158

Earlier quoted context omitted.

Even with the Cocoa styling, Qt based applications always seem to feel weird or out of place. Things like button placement, toolbars, things of that nature just don't "feel" right.

Thats the "weird" thing about Mac users: noticing that things "doesn't feel right" while completely missing that somebody has mangled their keyboard (where is home/end? pg up/pg dn? Waht are these extra arrow up left and arrow down right thingies on my keyboard that even long time Mac users cannot explain? (Feel free to explain it and I'll give you an upvote tomorrow morning if I remember : ) why is fn/ctrl switched…

I've got a full sized keyboard, I've got an home/end, a page up/page down, and I am wondering what you mean with extra arrow up left, and arrow down right?

Are you referring to the arrows that signify home/end/page up/page down on the older full size keyboards?

On the laptop keyboard the Fn key is the outer key, followed by ctrl, then alt/option and then command on my full size keyboard it is placed above the delete button and to the left of the "home" button. It's not switched.

Either way, you could replace your Mac keyboard with one of your standard Windows ones and everything will continue to work without issues. So if the keyboard layout is a bother, that is easily fixed. You'll just need to remember to hit the windows key to copy/paste rather than ctrl.

Re: GitUp makes Git painless

#242

Post by X-Istence »

alok-g wrote: post #236
X-Istence wrote: post #158

Earlier quoted context omitted.

Even with the Cocoa styling, Qt based applications always seem to feel weird or out of place. Things like button placement, toolbars, things of that nature just don't "feel" right.

>> just don't "feel" right. I would have understood this remark a few years back. After having made such remarks for the last several years, and after having so much work done on UI/UX studies, let's become engineers again and be able to specify exactly what is not right.

The size and location of buttons is off, the font rendering isn't as crisp, in some cases the buttons are swapped, developers tend to not follow the HIG and buttons are named differently from their OS X counter parts. The toolbar will use icons that don't fit in with the rest of OS X. Closing the primary window will sometimes take the whole application down with it, rather than just closing that particular pane of glass, right clicking on the icon sometimes won't display the windows that are open, drag and drop doesn't seem to work as well onto certain fields. Text sometimes renders wrong, or buttons are not made auto scale-able so you have text hanging off the end. Keystrokes you expect to work in text fields don't, no dictionary or auto-correct (although that was about two years ago when I last built a Qt based application for Windows/OS X).

The list goes on. It's the same sort of list that can be made with Java based applications. CyberDuck was one of the few applications that surprised me when I first started using it with how well it fit into OS X and I didn't realise that it was a Java application underneath the hood.

Ultimately it comes down to the application "feeling" out of place simply because it is out of place and wasn't built or designed with OS X in mind.

Re: GitUp makes Git painless

#244

Post by dallanlee »

I think your choice, swisspol, to use the 'free-with-in-app-purchase' model is the right one. You're selling to OS X users, who are willing to actually spend money on apps and software, and it allows us to use an app and then decide if we want to buy it. All that really needs to be said is, "GitUp is free with lots of capability to get things done. But to speed up your workflow even more and use all of its features, it offers an in-app purchase to upgrade." Plus, we as OS X users are used to noticing that little 'in-app purchases' note on apps and don't think it's a "slap in the face". I just hope that it will be available on the Mac App Store. I trust apps most that are sold on the App Store and I always look there first. I tie my card to my iTunes account or even have gift card money ready to make a purchase. Also, I can see when it was updated, what others say about it in reviews and share it quickly and easily. Just my thoughts, @swisspol

Re: GitUp makes Git painless

#245

Post by garthk »

copsarebastards wrote: post #201
hatsix wrote: post #118

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

'npm ls' might give you a clue.

Most mysteries come down to loose dependency declarations and semver stuffups, sometimes in combination. One of your deps' deps takes a ~ on one of its deps, that dep makes a breaking change and changes its version from 0.3.2 to 0.4.0… boom. Your fresh npm install on workstation #2 inhales the breaking change and doesn't work, but workstation #1 still works fine.

Fix: temporarily shrinkwrap from workstation #1 while you wait for the maintainer of the package with the ~ dep on the 0.* package to change to a ^ dep.

It's a machine. It's a lot more predictable than you think.

Re: GitUp makes Git painless

#246

Post by the_ancient »

camillomiller wrote: post #4
the_ancient wrote: post #2

>>Requires Mac OS X 10.8 or later Apparently it is not the interface I have been missing... Having a Git tool not available for Linux is blasphemy

Yeah how dare they develop a nice and useful tool, right?

Apparently you and everyone else in this thread do not know the History of git

git is a tool developed specifically for Linux Kernel Development, GIT would not exist with out linux.. Linus Torvalds created git for linux.....

So releasing any tool for git that does not support linux, IMO is betraying the history and foundation of git.

Re: GitUp makes Git painless

#247

Post by hobarrera »

`man git` make git painless. And it works on almost any platform.

I've also got to say I dislike how this makes history rewriting so simple, advertises it so much, but shows no warning as to the complications this can bring (anybody else using this repo will suffer greatly on the next pull!).

Of course, that's explains in the man page.

Re: GitUp makes Git painless

#248

Post by stcredzero »

jv22222 wrote: post #165
swisspol wrote: post #151

Earlier quoted context omitted.

Hey, it's called promotion and marketing, don't read too much into it ;) And it's not far at all from what a number of GitUp users are saying themselves: https://twitter.com/GitUpApp/favorites .

Well, I just saw that profitseduction.com says it's exactly the right thing to do (and that's a classy blog), so... I take it all back ;) http://profitseduction.com/are-you-afraid-to-make-a-bold-cla...

Thanks for trying to impress us with an appeal to authority.

Re: GitUp makes Git painless

#249

Post by copsarebastards »

garthk wrote: post #245
copsarebastards wrote: post #201

Earlier quoted context omitted.

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.

'npm ls' might give you a clue. Most mysteries come down to loose dependency declarations and semver stuffups, sometimes in combination. One of your deps' deps takes a ~ on one of its deps, that dep makes a breaking change and changes its version from 0.3.2 to 0.4.0… boom. Your fresh npm install on workstation #2 inhales the breaking change and doesn't work, but workstation #1 still works fine. Fix: temporarily shrin…

I understand how such things occur, but that's not an ecosystem I want to be involved in. If ~ frequently lets in breaking changes (and it does) then nobody should be using it--the entire point of having versioned dependencies is to prevent breaking changes from entering your system.

And tracking down these versions by hand is not a reasonable solution: some of these libraries pull down dozens of dependencies, each with their own dependencies, and it's not feasible to read the docs for every single package to find breaking changes.

> Fix: temporarily shrinkwrap from workstation #1 while you wait for the maintainer of the package with the ~ dep on the 0.* package to change to a ^ dep.

If I have to rewrite my entire install script to pull from a specific machine, the package system is useless, and I'll switch to a package system which is competently managed. What you're describing isn't a fix, it's a workaround.

In a larger sense, one of the main motivations for using other people's libraries is that libraries should "just work" and not need to be debugged and tested. That's not an assumption you can make in the node ecosystem. There are reasons you might want to test libraries, such as if you're writing crypto, or critical code on which people's lives depend. But the issues in node's ecosystem aren't that, they're just developers not following very basic development practices.

I stand by what I said: the node ecosystem is a mess. You've told me how to fix the node ecosystem's mess (which I already new) but the fact is, I have better things to do than constantly trying to fix other people's messes.

Re: GitUp makes Git painless

#250

Post by copsarebastards »

framp wrote: post #215
copsarebastards wrote: post #201

Earlier quoted context omitted.

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.

I disagree. It's pretty much the opposite from my experience. Are you using npm shrinkwrap?

I tried npm shrinkwrap, but that only procrastinates on the problem: now instead of having to unravel a mess of dependencies on installation, you have to unravel a mess of dependencies whenever you want to upgrade a package. But now instead of having to solve a dependency problem that a bunch of other people have head to solve, you've created your own unique dependency problem. Not to mention that this completely bloats your installations.

npm shrinkwrap isn't a solution, it's a temporary hack and it makes things worse in the long run. Maybe you're only working on new projects, but I work on things that will have to be maintained.

Post reply on HN