Skip to content

Instantly share code, notes, and snippets.

@ackvf
Last active March 31, 2026 08:20
Show Gist options
  • Select an option

  • Save ackvf/8dc3eacbe8fde2af0e5632ae62296565 to your computer and use it in GitHub Desktop.

Select an option

Save ackvf/8dc3eacbe8fde2af0e5632ae62296565 to your computer and use it in GitHub Desktop.
I hate prettier and you should too.

This is why I hate prettier and why you should too

This here is a collection of reasons why I genuinely, viscerally dislike Prettier. There’s nothing “pretty” about any of this, and it’s not really “the same” either. It’s just deterministically ugly for everyone in exactly the same way — that’s its only real benefit: eliminating arbitrary cosmetic diffs and drift.

Human evolution has optimized us to be exceptionally good at recognizing visual patterns. Our perception is highly sensitive to similarity, symmetry, proximity, alignment and predictable grouping (Gestalt principles).
Therefore indentation, grouping and alignment become cognitive shortcuts.

When a formatter breaks these (e.g., awkward line wrapping, misaligned constructs (e.g. operators)), it increases cognitive parsing cost, even if the code is technically “consistent.”

On the other hand, Prettier's goal was never optimizing for readability. Its design goals were:

  • eliminate formatting debates
  • enforce consistency
  • reduce diff noise

Prettier

@ackvf
Copy link
Copy Markdown
Author

ackvf commented Mar 31, 2026

Gestalt Principles

image

@ackvf
Copy link
Copy Markdown
Author

ackvf commented Mar 31, 2026

On the left is manually formatted code with ESLint. On the right is machine-formatted output.

In other words:

  • On the left, the code is written by a human (with AI assistance) and formatted by a human for humans.
  • On the right, the code is regurgitated by a machine for machines. Human readability drops dramatically.
image image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment