Ten years ago today, @mike-burns made the first commit to rcm, starting with just relatively simple mkrc and rcup commands. While it didn't start out with many of the options and features we know and love today (hooks, multiple dotfile dirs, exclusions), it had many core features from the very beginning like the rcrc config file, tags, and host-specific files.
I began my switch over to rcm in 2016, moving from @docwhat's homedir project after 9 years. (Somewhat humorously, I just noticed that he moved to rcm in 2014, so apparently I was still using homedir long after he had moved on.)
Despite all of the other dotfile management tools that have popped up in recent years, rcm has always hit the sweet spot for me in terms of simplicity, focus, and portability. So thanks @mike-burns for starting the project, choosing to open source it, and for keeping it going all these years. Thank you to @thoughtbot for sponsoring Mike's work all this time, and thanks to the dozens of contributors over the years.
Ten years ago today, @mike-burns made the first commit to rcm, starting with just relatively simple
mkrcandrcupcommands. While it didn't start out with many of the options and features we know and love today (hooks, multiple dotfile dirs, exclusions), it had many core features from the very beginning like the rcrc config file, tags, and host-specific files.I began my switch over to rcm in 2016, moving from @docwhat's homedir project after 9 years. (Somewhat humorously, I just noticed that he moved to rcm in 2014, so apparently I was still using homedir long after he had moved on.)
Despite all of the other dotfile management tools that have popped up in recent years, rcm has always hit the sweet spot for me in terms of simplicity, focus, and portability. So thanks @mike-burns for starting the project, choosing to open source it, and for keeping it going all these years. Thank you to @thoughtbot for sponsoring Mike's work all this time, and thanks to the dozens of contributors over the years.