Which should you use for a distributed version control system (DVCS) – git or mercurial? That was the question taken up recently by two opposing blog posts on Atlassian’s blog:
Admittedly this is a bit of a “religious” issue with adherents on either side being extremely passionate about the topic. In my own case, my writing here (as well as my Github account) definitely show that I fall down on the side of git… but I’m also always interested to learning more about the various tools.
The two blog posts are written by passionate advocates for each tool and so naturally have that flavor. Regardless, they make for interesting reading. I don’t see myself switching to Mercurial any time soon… but it’s interesting to see the pros and cons of each. We still don’t have the “perfect” tool… but will we ever?
Given that I started working with version control systems back when RCS was the only option I had… and then CVS was a huge step forward… and then SVN was viewed as excellent… all I can say is that we’ve come a loooonnngg way and it’s greatto see both git and mercurial out there.
P.S. I should note that both of these articles are part of Atlassian’s “DVCS Guide” that has some other useful pieces about why distributed version control systems are worth investigating and using.
Interesting to see that the White House is sponsoring its first ever code sprint… from the announcement back on April 2nd:
Today we’re announcing the first ever White House Code Sprint. This is a call to developers around the country to use the Summer Jobs+ API to build job search apps for your favorite browsers, social networking platforms, smart phones and feature phones. Submit your apps using this form by Monday April 16th at 8 a.m. EST, and we’ll pick the most innovative ones to feature on WhiteHouse.gov.
The Code Sprint web page says a little bit more:
The White House and the Department of Labor have just released an API opening access to thousands of summer internships, training and mentorships opportunities through their Summer Jobs+ Bank. We’re challenging the developer community to build apps that reach kids throughout the nation on their browsers, Facebook, Android, iOS, SMS or any other platform.
This is the first ever White House Code Sprint and we’re excited to see what innovative apps you build over the next seven days. There is no ideal app, but keep in mind that our goal is to share opportunities in our job bank with as many youth as possible.
It’s good to see the White House seeking to tap into the energy and passion of the developer community… I don’t personally have the time to participate in this event, but I hope they do get some interesting application submissions. My one comment is that they didn’t allow much time… they issued the notice on April 2nd with a deadline, then, of April 9th. Not much time to publicize it and get interest… but we’ll see.
If you are interested, the deadline has been extended to this coming Monday, April 16th.
Want to learn more about Node.js, a topic I’ve frequently written about here? If so, a friend recently pointed me to an excellent collection of Node.js-related links compiled by Stanislav Stoyanov:
My Node.js Linksheet
(UPDATE 5 Mar 2013: It seems that the site may unfortunately no longer be available. In a quick search online I was unable to find any alternative sites hosting the document.)
It’s a great collection of companies, tools, games, platforms, frameworks and more all associated with Node.js. While Joyent also maintains a list of Node.js resources, this list from Stanislav Stoyanov contains many excellent pointers for those looking to learn more and get started with Node.js.