pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: vlsi (@vlsi) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: [pgjdbc/pgjdbc] issue #3635: Consider migrating from spaces to tabs
Date: Wed, 21 May 2025 19:27:23 +0000
Message-ID: <[email protected]> (raw)
See
* https://www.reddit.com/r/javascript/comments/c8drjo/nobody_talks_about_the_real_reason_to_use_tabs/
>i get approached by not one, but TWO coworkers who unfortunately are highly visually impaired,
and each has a different visual impairment
> * one of them uses tab-width 1 because he uses such a gigantic font-size
> * the other uses tab-width 8 and a really wide monitor
> * these guys have serious problems using codebases with spaces, they have to convert, do their work, and then unconvert before committing
> * these guys are not just being fussy — it's almost surprising they can code at all, it's kind of sad to watch but also inspiring
Code with tabs consumes [fewer cells on braille displays](https://stitcher.io/blog/tabs-are-better).
Code with tabs consumes the same or bigger amount of tokens when using [ChatGPT 4o tokenizer](https://platform.openai.com/tokenizer). For the small files the number of tokens is more-or-less the same, and a bigger [TrieNode.kt](https://github.com/Kotlin/kotlinx.collections.immutable/blob/bd5ac10f1e3b72c8bd6335005bf27d751e0d8b5...) consumes 8958 tokens (32462 chars) with tabs, and it consumes 8859 tokens (37757 chars) which means 1% more LLM tokens when using tabs :-/
Of course, changing the spaces to tabs would be disruptive, however, it might bearable. I've not explored it yet.
However, it looks going with tabs is the right thing to do.
See:
* https://x.com/Rich_Harris/status/1541761871585464323
* https://github.com/prettier/prettier/issues/7475
* https://stitcher.io/blog/tabs-are-better
* https://youtrack.jetbrains.com/issue/KT-77740/Consider-moving-Kotlin-style-guide-to-tabs-for-the-acc...
view thread (4+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] issue #3635: Consider migrating from spaces to tabs
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox