Hey everyone,
I’m trying to decide between using a simple file system or a hosted Subversion service for version control. My company already has a group managing Subversion, which offers:
- No maintenance for us
- Automatic backups
- Built-in file history, merging, and diff tools
The file system approach is simpler but lacks these features. However, if we use a Linux machine with backups, it could handle file system issues. Subversion would need working copies on the same machine anyway.
I’m leaning towards the file system for simplicity, but I’d like to hear some strong arguments for choosing Subversion instead. What are your thoughts? Have any of you faced a similar decision?
Thanks for your input!
Note: I’ve already looked into commercial options and decided against them for our needs.
hey zack, interesting dilemma! have u considered the collaboration aspect? subversion might be better for team work, but it depends on ur project size. How many ppl are involved? And wat about future scalability? curious to hear more bout ur specific needs. maybe theres a middle ground solution?
As someone who’s worked with both systems, I’d recommend Subversion for your situation. While a file system approach might seem simpler initially, Subversion offers significant advantages in the long run. The built-in version control features—such as branching and merging—can save considerable time and headaches, particularly as your project grows. Additionally, the automatic backups and centralized repository enhance the security of your code. Given your company’s existing Subversion infrastructure, it is both a logical and efficient choice, allowing you to focus on core development activities.
yo zack, i’d say go with subversion. its already set up, so why not use it? file system might seem simpler, but subversion gives u those sweet features without extra work. plus, if ur company grows, you’ll thank urself for choosin a proper version control system. just my 2 cents!