6 ms·
They take backups, name each folder based on the date, and what feature that was just completed (or just about to be started) that prompted the backup. I bet yo
by tom_ 8y ago
They take backups, name each folder based on the date, and what feature that was just completed (or just about to be started) that prompted the backup. I bet you a pound.
This is what everybody that says they don't use version control does.
- chimeracoder 8y ago> They take backups, name each folder based on the date, and what feature that was just completed (or just about to be started) that prompted the backup. I bet you a pound. All they need to do is to compress those folders with zlib, and then they've reinvented git.
- peheje 8y agodiff, branch, merge, blame, stash
- a1369209993 8y agoThat's what I do (for personal projects where I don't care about complex commit-graphs) and I do call it version control.
- chucksmash 8y agoJustifications like "where I don't care about complex commit-graphs," of which there are a few in this thread, always sound like they're trying to hide confusion about the tool by making it sound overly complex. Nobody cares about complex commit-graphs! If you're just one person, you can work directly on master and just commit everything every time: git commit -am "I did some work" Don't try to follow gitflow or githubflow or whatever it is that's made you bail on real version control. But why play the copying folders monty game in 2019?
- a1369209993 8y agoYou don't seem to understand my previous comment. Tarballs are better. Complex commit-graphs are not a reason to avoid git for small projects, they are a reason why I can't avoid git for large projects. The revision history is complex or not regardless of what software I'm using to slog through it.
- Moru 8y agoNonono, that method existed long before Git. Git reinvented the wheel, if they did a better job about it is not for me to judge :-)
- c3534l 8y agoSo they don't use version control software.
- Eruvarn 8y agoBut if you're going to go through all that work... isn't it easier to just use Git, or some other VC?
- AnIdiotOnTheNet 8y agoI've used git when I've contributed to open source projects. It's an over-complicated mess of a system when you're just one or two devs. Regular backups and notes are more than sufficient and never require you to google how to unfuck your branch.
- leadingthenet 8y agoThere is a learning curve, true, but it definitely pays off once you are comfortable enough with the (admittedly bad) UI. Even for 1-2 person teams.
- AnIdiotOnTheNet 8y agoI disagree. Compressed backups of the source and a changelog are very simple, straightforward, and effective on this scale. Too many people in this industry fetishize complexity and end up over-complicating even the smallest things, which might be why they get on the internet and criticize someone like Tarn for not doing so instead of actually creating something worthwhile.
- leadingthenet 8y agoHow the heck is that simpler than -- git add . -- git commit -m "I did something" -- git push How???
- joppy 8y ago“git show-me-the-code-as-of-last-Wednesday” is not a command that git understands. Of course, you can _do_ this in git, by memorising arcane commands, and you still only get the output on your terminal. The other option is basically using a GUI interface for git. On the other hand, finding the folder for last Wednesday and opening it up is easy.