>Whitespace indentation is used for denoting structure; however, tab characters are not allowed as part of that indentation.

>>106038261 (OP)
What is the use case? I mean for configuration maybe but for serialization significant white space can be a waste of space.

>>106038261 (OP)
I would rather be homeless than write another line of yaml.

>>106038261 (OP)
it's json but with less brackets

>>106038295
Basically JSON but much more pleasant to write and it has comments

>>106038295
You can omit a bunch of quote marks though, and if you’re really trying to reduce over-the-wire space taken you can just output YAML in the flow style so it looks like JSON
'@context': https://schema.org/
'@type': Recipe
name: ChefSteps’ basque cheesecake
url: https://www.chefsteps.com/activities/basque-cheesecake
author: Nicholas Gavin
cookingMethod: baking
recipeCategory: dessert
tool:
- '@type': HowToTool
name: 4-qt. Cambro
description: a 4-quart tall, narrow container
sameAs: https://www.amazon.com/Cambro-Containers-Lids-Food-Storage/dp/B07K5DGWNR?tag=chefsteps02-20
- immersion blender
- instant-read thermometer
- nonstick cooking spray
- parchment paper
- fine-mesh strainer
- 9″×3″ springform pan
- half-sheet pan
- cooling rack

# Todo: add grouping
recipeIngredient:
- { '@type': PropertyValue, value: '1.4', unitCode: kg, name: cream cheese, description: ≈6⅕ 8-ounce (226g) bricks }
- 450g granulated sugar
- 65g AP flour, unbleached
- 8g kosher salt
- 700g heavy cream
- 9 eggs, large
- 15g vanilla extract

This would be more unpleasant to write as JSON

>>106040160
Looks like shit and is slow to parse

>>106038261 (OP)
>json
>6 charts
>yaml
>10 chapter plus errata
https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell

>>106040021
>much more pleasant to write

>>106038261 (OP)
stop using useless tab characters. simple as lmao

>>106038261 (OP)
>muh tabs
tell me you're a lazy subhuman nigger without telling me you're a lazy subhuman nigger