scottayy wrote:
However, the one I refuse to change (maybe it's my immaturity) is using 4 spaces instead of tabs. I don't think I will ever change that. Tab is just way easier, in my opinion. And I've been used to it since back when I started writing HTML.
Is that that much of a big deal? I mean most editors come with a function that converts tabs to spaces and vice versa.
I don't want to start the tabs vs spaces debate though.
My point of this topic is do you conform to coding standards? If so, which? Was it hard to get into practice of using the standards? Are there any (like me) that you just refuse to use?
Definitely not starting the debate, or continuing it, but just wanted to point out the logic that led me to a different conclusion.
The tools in use: Putty on Windows, Firefox viewing the websvn on sourceforge, and nano on linux as the text editor.
Copy and paste from firefox, into nano via putty. Tabs are pasted as spaces. Now do a svn diff. Guess what? They are
different than the code you are viewing - resulting in an incorrect diff.
It makes it impossible to use that set of tools. Further, nano doesn't offer a way to view tabs as spaces as far as I know.
Tabs have plenty going for them, but cut-n-paste across multiple platforms isn't one of them. Tabs is good for compatibility between different coding styles, spaces is good when you need the code to be consistent
no matter what.
So, I went with spaces. There is almost never a time when a piece of software cannot consistently display four spaces.
