- Text searchable
- Easy to adjust
- Supported by a surprising number of markdown viewers.
png diagrams should never be the default.
graph TD
User -->|Enters Credentials| Frontend[React App]
Frontend -->|POST /auth| API[NodeJS Service]
API -->|Query| DB[(PostgreSQL)]
API --x|Invalid| Frontend
DB -->|User Object| API
API -->|JWT| Frontend
and +-------+ +-------------+ +---------+
| User | | React App | | NodeJS |
+-------+ +-------------+ +---------+
| | |
| Enters Creds | POST /auth |
|--------------------->|---------------------->|
| | |
| Invalid | <-- [X] Error -----|
|<---------------------| |
| | Query DB |
| |---------------------->| [ DB ]
Plus while an LLM can understand relationships via pure ASCII or an image, it's just easier to give it the relationship data directly.It’s harder to read mermaid in a terminal or a markdown file…
(Not to take anything away from Monosketch, which is cool.)
This is not historical reasons, this is just that moving my hands from the keyboard to the mouse is inefficient and technically unnecessary. I prefer mouse only on niche (for me) tasks like screenshot cropping or something.
I am about to test out Niri on my laptop and I expect to be quite pleased with the change.
A car has had largely the same shape since its creation, indeed since antiquity.
Sometimes, a problem space is explored to most humans' needs, and no more innovation is needed.
(edit: this said, I'm hopeful there is something new, and people like Bret Victor may show the way with things like https://dynamicland.org/ )
ASCII to me represents something that can work in my term, in my source code, checks into git a bit more sanely than binary does, etc.
I still quite like it