News for hackers. Stuff that matters.
Re:Data Loss at GitLab by Thaxll on Wednesday February 01, 2017 @06:43PM (#13546599)
You code differently using Git vs SVN? That's an interesting concept. It doesn't change the way you code it just changes the way we share code.
Re:Data Loss at GitLab by jasonwatkinspdx on Wednesday February 01, 2017 @09:14PM (#13547497)
Git makes multi-tasking on multiple branches far easier than SVN. In the SVN days I always had multiple checkouts and a pile of scripts for changing/updating to branches for handling a few regular tasks in that context. Once git won I was able to delete them and have a far simpler workflow.
Re:Data Loss at GitLab by gowld on Wednesday February 01, 2017 @06:56PM (#13546694)
It doesn't change how I code. It changes how we code.
Re:Data Loss at GitLab by nstj on Wednesday February 01, 2017 @09:23PM (#13547550)
Git absolutely changes the way I code. Cheap feature branching and easy rapid collaboration are huge in how they influence my coding practice and output. I wouldn't enjoy coding anywhere near as much if it weren't for Git.
Re:Data Loss at GitLab by VintageCool on Thursday February 02, 2017 @12:55AM (#13548439)
A few months ago I was developing for a breaking change and realized that I wasn't committing anything. That's very much an SVN mindset where merging is so painful that you culturally just avoid it altogether. Git's emphasis on being distributed and branching and merging constantly meant that, once I pulled my head out of my ass and started committing locally, I was able to enjoy the benefits of source control while developing my breaking changes without affecting anyone. And later, when I merged my branch into the master, it turned out to be completely painless.