I have never understood the essential difference between a tab and a series of spaces but then again I have never tried since I mostly run into the problem when I have to use word and word only makes sense according to the logic of people inside the alternate dimension of microsoft which as far I know scientists have been unable to prove has any connection to logic in the outside world.
@Alonealastalovedalongthe @cypnk All the small practical savings like tab being one character versus spaces being 4 (in most cases), the one compelling argument that made me change my opinion is that for you, there may be no difference between tabs and spaces, but for someone with accessibility requirements such as for example large fonts, it is important to be able to change the visual appearance of indentation, for instance to fit more large text on the screen.
@mdhughes @cypnk And then there is the people who are obsessed with variable alignment which can only be done with #space and the single reason we are stuck with #spaces . Fuck I wish I could use #tabs most of the times but editors are always stopping me from using #tabs or just outright just hide it and tell me they're #tabs when they're really #spaces behind the scenes (I'm looking at you Emacs).
While I agree that tabs are the most logical whitespace choice that allows you to "bring your own tabwidth" to any project with fewer characters per file all around, if I can't look at a fucking file/code snippet on github/gitea/gitlab/gitwhatever/forum without scrolling to the right I might murder someone. Spaces set a standard.
@cypnk I wish vim had a mode that were like, "pages", but really tabs in disguise.
the way we display tab-based indentation is just awful and confusing.
The original server operated by the Mastodon gGmbH non-profit