Source control does matter. If you're thinking about any serious development effort (startup or not), you really need to use it. Unless of course you can honestly say that you always know exactly what your next step is, never make any mistakes, never need to go back to an old version and work with a group of identical equally perfect developers.
What you need to figure out is which tool (git, svn, or something completely different) matches with your style and needs as a developer or group of developers. The best version control is the one that becomes part of your natural workflow so you use it without thinking of it as an extra step that you constantly have to do. Because if that happens, you'll just stop using it.
Git's branching capabilities work well for someone who needs to work on multiple independent features or try out new ideas that may or may not work out. All of which is usually what's going on in a startup. It's something that comes as part of the tool instead of having to be worked up in a series of processes that you don't either have to time or (painful) experience to come up with yourself.
What you need to figure out is which tool (git, svn, or something completely different) matches with your style and needs as a developer or group of developers. The best version control is the one that becomes part of your natural workflow so you use it without thinking of it as an extra step that you constantly have to do. Because if that happens, you'll just stop using it.
Git's branching capabilities work well for someone who needs to work on multiple independent features or try out new ideas that may or may not work out. All of which is usually what's going on in a startup. It's something that comes as part of the tool instead of having to be worked up in a series of processes that you don't either have to time or (painful) experience to come up with yourself.