General > General Technical Chat
Religious technical opinions
<< < (10/22) > >>
PlainName:

--- Quote ---But its the "why do I care" that is telling
--- End quote ---

That's what struck me, too.
eugene:
I might ask the question: are you saying that everyone, including me, should use [spaces | tabs], or are you saying that you personally prefer one or the other for your own use.

I'm neither agreeing or disagreeing with free_electron, but he does have the advantage in that he's not trying to tell me I'm wrong in some way.
free_electron:
It doesn't matter to me what you are using ( spaces , tabs , tabs converted to 3 spaces, tabs converted to nine spaces ).
Use whatever you want. i don't care because it is not a problem. (unless dealing with python , but that too is not a problem. i refuse to use that freakshow) . 

There is no 'standard' for indentation or tab to space conversion. Whenever you use some library it all seems to be done differently. Oracle Java specs a tab as 8 characters..
If i will use your code i will load it in an IDE that cleans all that stuff (ya ya not automatic it takes a hotkey or menu action . so what ? ) and properly indents it according to MY rules. The way I want to see it.



alexanderbrevig:
I don't get why people still argue about tabs vs spaces!?
Which leads me to some opinions:


* git is the best VCS, it can handle check in/out and keep tabs or spaces as is by file
* 80 chars are not the only char width that makes sense (thank you, punch card storage boxes)
* vim is the only editor, vim is the best editor, if you disagree you've not really tried it (or using emacs which is fine) <vim makes me forget tabs vs spaces is a thing>
* private members does _not_ belong at the top of the file, give me what I probably come looking for first
* code style does not matter, good tooling does, autoformat on save all the things => smaller git diffs
* "not invented here" is just as bad in hardware design as it is in software, yes you can probably trust that footprint that's been used since 2005 by countless projects, even if you did not draw it yourself.
* if you cannot automatically test what you've made, you're doing it wrong
* hating a programming language only means you're not an expert in it
* embedded developers use way too much magic in their code, the compiler is our friend, let's make use of it!
In all honesty though, if you've got a colleague with bad vision: Show them vim!
They will love the "not hunting for the cursor" aspect of the typical IDE experience, and of course the ability to set tab width that works for hard and soft tabs.

So there, that's my head on the chopping block :D  :box:
Someone:

--- Quote from: eugene on February 24, 2022, 10:53:12 pm ---I might ask the question: are you saying that everyone, including me, should use [spaces | tabs], or are you saying that you personally prefer one or the other for your own use.

I'm neither agreeing or disagreeing with free_electron, but he does have the advantage in that he's not trying to tell me I'm wrong in some way.

--- End quote ---
There is no general reason to prefer one or the other if you write code for yourself. You are not wrong for picking either, they are wrong for saying that it does not matter since their choice of text editor hides the differences (or worse, forcefully changes it to a specific indentation method+pattern).

If you share work on code (particularly through a change tracking system such as git) and people need to edit each others files, then it becomes an issue. Editing text is a small part of delivering "code".

Many text editors/IDEs will "work" with tabs or spaces (even with varying "sizes" for tabs), but you need to be careful not to make unnecessary changes when returning files with your new changes. Generally most people continue whatever indentation is already used in the file, or for a new file some agreed upon standard within the team/group. But feel free to be that one guy who no-one wants to work with if you insist on using your preference against whatever is already in place.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod