Cornerstone vs Versions

I dont know how long Cornerstone has been around (actually, according to their blog it looks like the first version came out around May 2008), but i only learned about them last week (an ad in Tweetie), and immediately downloaded it.  I spend all day every day working with code stored in different Subversion repositories.  Up until now, I have been using Versions as my Subversion app of choice, and its been great.  There are a few annoying issues with Versions, and i’ve been surprised at how long they take between releases, but it was the first Subversion app for the Mac that was actually worth using.

Coming from having used Versions for a long time (I was the second ever paid customer when it came out of beta), i had – and still have – a little difficulty finding the button im looking for in Cornerstone.  Some actions are in the top toolbar, and some are down the bottom.  I often forget where each button is.  But aside from that, I have found it has a bit of an advantage over Versions…

Number of changed files badge

Changes count badge

I have many local copies of repositories on my computer.  I loved the feature in Versions where it would show you a badge with the number of changed files… until I realized that was the reason my computer ground to a halt so often.  Thankfully, Cornerstone is a little more intelligent about it.  Im not sure how its done, but its like Cornerstone has hooks in the system that notifies the app when files are changed in certain directories.  In Versions, it seems to be constantly scanning for changes, but in Cornerstone, it seems to know with directories have had changes, quickly scans through those directories to find the changed files, and shows me the little badge, all very quickly, and without noticeably degrading system performance.

Logs

Versions is very slow at dealing with viewing commit logs.  It fetches the logs from the server every time i want to look at them, but Cornerstone fetches the list once and caches it… then it just fetches the updated logs (I am assuming this is how it works, it certainly appears to work this way), meaning that after the initial download of logs, browsing commit logs in Cornerstone is super fast.

Viewing diffs

Cornerstone has a built-in diff viewer which is nicer than the File Merge app included with Xcode – but you can also choose to use an external viewer if you want.  Versions doesnt have a built in diff viewer, which is not a bad thing, but i do find it handy being able to click the Compare with Base button in Cornerstone and not have to wait a few seconds to open an external app.

Timeline

Cornerstone has a timeline viewer which Versions doesnt have.  It reminds me of a gantt chart.  It adds a nice way to visually see changes over time.  Being a visual person, i like it.

Resolve

I’ve only been using Cornerstone for a week or so, and havent had a chance to use the Resolve feature yet, but im very interested to see how well it works, and how useful it is.

SSL

I use Storehouse to host my repositories (obviously), and one issue with Versions (actually I think its more of an issue with Subversion itself, I should find out) is that it has issues with wildcard SSL certificates.  Storehouse has a single SSL certificate for *.storehouseapp.com which means that all clients who use domains like client.svn.storehouseapp.com to access their repositories can use SSL.  In Versions, every time you add a repository that uses a wildcard SSL certificate like that, it alerts saying the certificate isnt valid (which it most certainly is), and you have to manually accept the certificate.  This is a common problem and other hosted Subversion services face the same issue.
When I add the repositories to Cornerstone, I didnt get any warnings about the certificate and it worked very smoothly.

I also appreciated the drop-down to select a recently added repository as more often than not, only the actual repository name needs changing when adding new ones.

Committing

When you’re committing a few files in Cornerstone, you can select the files, press Commit, then see the list of files and write the commit message (same as Versions), however, in Cornerstone, you can then select any of those files to do a list minute diff, you can untick some files you accidentally selected.
Also, while the files are being sent to the server, the whole interface isnt locked up.  In Versions, you cant do anything until the commit has finished (unless you have multiple windows open which is messy).  In Cornerstone, you can carry on sorting out the next commit in the same or any other repository while the previous commit is still being sent to the server.

Wrap-up

Cornerstone feels like it has more power than Versions, but i think Versions feels like it has a tidier interface.  I guess less buttons makes it feel easier.

I havent actually purchased Cornerstone yet, Im still running the 14-day trial (Im unsure how long the Versions trial lasts).  They both cost around US$59 (actually Cornerstone is exactly US$59, and Versions is priced at EU39 which is around US$58).
I havent yet decided which app to use as my Subversion app of choice, but i think im leaning towards Cornerstone.

Does anyone have any stories of using either Versions or Cornerstone?  I’d be very interested to hear them.

Obviously, the logos and app names are copyright of their respective owners.

Related posts:

1. Subversion 1.6 quick reference card

“It’s common practice for any software project with multiple coders to use some version control mechanism. CVS or Subversion used to be popular. These days distributed systems like git and Mercurial are the quickly replacing the old standards. But what about the cases when you’re the only coder?”

by Fraser Hess via cimgf.com

Have a look at Storehouse – Easy Version Control.

Related posts:

1. Storehouse App launched – Hosted version control
2. Recipes App – Version 1.1
3. Mac subversion apps – Cornerstone vs Versions

“When Leopard was introduced, backing up became an automatic and effortless operation. Set it and forget it. Unfortunately, Time Machine backups are not off-site and don’t protect you against an on-site disaster. When I previously covered some online off-site backup solutions, Apple’s backup utility was not one of them.”

by Dave Greenbaum via The Apple Blog

No related posts.

Related posts:

1. Why version control is important for solo developers
2. Recipes App – Version 1.1
3. Mac subversion apps – Cornerstone vs Versions

“Wait a minute, Chrome OS ships with the Gnome desktop environment, OpenOffice, and GIMP? I thought the whole point was that it was purely web-based?

Update: Ah-hah, it’s a fake. Just some scammers hosting on Google Sites. No wonder I was confused. I can’t imagine that Google is OK with this.”

via Daring Fireball

No related posts.

“Over the past year many organizations are noticeably starting to “get” the importance of web application security and studying up on the issues, but experience doesn’t come overnight. At WhiteHat we meet a lot of different people possessing a variety of views on the webappsec world. So a couple days ago, I was sanity checking some of Bill Pennington’s (VP of Services) slides on “Five Things Every Security Professional Should Know about Website Security”. For some reason the way the advice was laid out it reminded me of the Five Stages of Grief (if your familiar) because it closely mimicked the attitudes of those we encounter depending on their degree of webappsec sophistication.  Bill re-did the stages, webappsec style, and it came out pretty funny actually…” via Jeremiah Grossman

No related posts.

Web app developers spend most of our time not thinking about how data is actually transmitted through the bowels of the network stack. Abstractions at the application layer let us pretend that networks read and write whole messages as smooth streams of bytes. Generally this is a good thing. But knowing what’s going underneath is crucial to performance tuning and application design. The character of our users’ internet connections is changing and some of the rules of thumb we rely on may need to be revised….  Read the rest of the article at developer.yahoo.net

No related posts.

“Coda is awesome. Here’s a quick way to make it awesomer: invisible visible invisible characters!” – Justin via justinhileman.info

Coda lets you show all the newlines, tabs and spaces, which comes in handy. But the default settings are pretty distracting. If you change the invisible character display color to match the background, they only show up when you select text.

First do this:

Then change this:

And rock out like this:

Related posts:

1. Web development tools

“Here’s a screen shot to contemplate.  There are two 140-character messages. Each illustrates features of the new shipwreck I hope to sink, to create a new coral reef for Twitter-like systems to grow on and around.” – Dave Winer via scripting.com

Related posts:

1. Quick idea of the day – Facebook/IMAP connector

Either Facebook should develop an IMAP system to read and reply to Facebook messages (Im only talking about the Mail, not wall posts or anything silly like that), or someone should develop a third-party system that integrates Facebook mail with IMAP.

I dont know a lot about the Facebook API’s but I would hope there was some way to access your own Mail messages through the API.  I also dont know a lot about how IMAP is built, but in my mind either an IMAP plugin (if such a thing is possible) to fetch mail from Facebook, or simply a system that fetches mail from Facebook using the credentials supplied by the user and pushes them into an IMAP system (tweaking the headers to put in a different Reply-To address – something like “reply-FACEBOOKMESSAGEID@fbmail.com” – so replies would go back to this third-party system which would then push the reply back into Facebook).

Related posts:

1. Subversion 1.6 quick reference card
2. Skype on the iPhone
3. Web development tools