3 ms·
Version control in general is not meant for "ordinary users"; it's for developers. I mean, sure, it can serve as a versioning system for just about anything, bu
by tdavis 18y ago
Version control in general is not meant for "ordinary users"; it's for developers. I mean, sure, it can serve as a versioning system for just about anything, but it is overwhelmingly used for code. Git doesn't need to be easy for my Dad to use because he has no use for it.
Despite having lived partially on the command line for nearly a decade now, there are still commands that are simply not intuitive to me. This isn't the developers' fault, it's my fault for not becoming more familiar with the commands and understanding why they actually make sense.
find $directory -type f -name '<asterick>' -exec mv {} $directory2/. \;
If you want to move thousands of files and can't use a single mv command, something like this will work. Most of it makes sense to me, but what's with the {}? That doesn't seem intuitive. And what about the extra /. \ crap? I would never think to add that junk and without it (iirc) the command returns some esoteric error.
I'm sure if I read the proper manpages, I could figure out what purpose those seemingly extraneous symbols serve.
- DenisM 18y agoAs others mentioned, cvs is not just for developers, it's also for doc writers, lawyers, UI testers and designers. All that goes into a product must be versioned. But fine, let's say it's for developers only. Did you notice that the article is written by a developer? Clearly GIT is too difficult for some of its core aduience - developers. Blaming the user is not the way to build something people want.
- tdavis 18y agoYes, some, but not most. I switched from Subversion to Git myself a couple months ago and it took a week or two, but I learned "the git way" of doing things. Yes, I would need to look up the command to remove a remote branch, but I haven't done it in weeks and didn't commit it to memory the first time so that's understandable. Building something people want doesn't really need to be a goal of open-source software. Most software is built in the first place to solve a need of the person or people building it. Since they're not getting paid, what do they care if everybody wants to use it? A large majority of people seem to like Git. There will always be those who do not and I'm sure everybody has something they dislike about it. The difference is, Git is not commercial software, so making it more usable need not be an overwhelming goal -- although, you could fork it and make it your goal.
- scott_s 18y agoIf a person picks up a chainsaw, and then complains that pruning roses is difficult, this does not necessarily mean the chainsaw is ill-designed.
- blasdel 18y agoThe '{}' is where 'find' substitutes the filename into the '-exec' expression. The '/.' is pointless but harmless, conservative ass-covering, likely because the author was burned by leaving off a trailing slash before. They're already restricting types to files anyway! The semicolon terminates the -exec expression, and has to be escaped with a backslash so that the shell won't interpret it.
- tdavis 18y agoThank you! My intuition was correct about the '{}', but the rest was educational.