Like to rate videos and let people know what you think?
Automatically share your ratings, favorites, and more on Facebook, Twitter, and Google Reader with YouTube Autoshare.
Autoshare makes certain YouTube activities public on the services you choose. Select only the services you are comfortable with - like Facebook, Twitter, or Google Reader - to let your friends know what you like on YouTube. You can turn Autoshare off at any time.
Like to share videos with friends?
Automatically share your ratings, favorites, and more on Facebook, Twitter, and Google Reader with YouTube Autoshare.
Autoshare makes certain YouTube activities public on the services you choose. Select only the services you are comfortable with - like Facebook, Twitter, or Google Reader - to let your friends know what you like on YouTube. You can turn Autoshare off at any time.
I have really enjoyed your presentation. It is very creative and easy to understand. However, there are two controversial uses you have proposed:
- "Easy transfer to other people machines" . This is not the purpose of a Control Version System: could be abused and derive in "oh, please, commit this file, I need it at home. I don't care if it does not compile."
- "Backup". Please, don't use a CVS as backup. Same problem as above: People commiting files that don't work to not lose last changes.
Yep, you're right on target. Though I didn't produce the video personally, I think what we meant was that backup and ease of transfer are two handy side effects you get in cases where you were going to commit anyway.
Of course, if you go off on a branch, you can feel much freer to commit half-finished stuff, depending on your philosophy.
If you're assuming I'm a fan of VSS, I'm not. I use svn everyday. However your 'it costs more' analogy is flawed - Perforce is extremely pricey but it also happens to be the best SCM out there.
I've looked into Perforce before when assessing a large number of version control systems for our company. I really can't see any single killer advantage that persuades me it's worth spending money on Perforce, but everyone's requirements are different I suppose.
Autoshare makes certain YouTube activities public on the services you choose. Select only the services you are comfortable with - like Facebook, Twitter, or Google Reader - to let your friends know what you like on YouTube. You can turn Autoshare off at any time.
- "Easy transfer to other people machines" . This is not the purpose of a Control Version System: could be abused and derive in "oh, please, commit this file, I need it at home. I don't care if it does not compile."
- "Backup". Please, don't use a CVS as backup. Same problem as above: People commiting files that don't work to not lose last changes.
Of course, if you go off on a branch, you can feel much freer to commit half-finished stuff, depending on your philosophy.
The paper board says "- version control for files".
That's not what subversion is.
It is quite specifically version control for tree hierarchies.
CVS was version control for files, which turned out to be a bad idea with severe limitations.
Subversion did away with file based revision control in favor of a better model.
Just sayin'.... :)
... whereas Subversion is completely free and works on every operating system you can think of (and many you've never heard of).
How's that for a comparison?
So unless the free software is missing some absolutely vital feature that the expensive software has, a comparison is largely pointless.