𝕂𝚞𝚋𝚒𝚔ℙ𝚒𝚡𝚎𝚕<p>🧵 …additional article about the YAML <a href="https://chaos.social/tags/game" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>game</span></a> above, this explains why YAML is more <a href="https://chaos.social/tags/complex" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>complex</span></a> than many people realize.</p><p>»The YAML document from hell:<br>For a data <a href="https://chaos.social/tags/format" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>format</span></a>, yaml is extremely complicated. It aims to be a human-friendly <a href="https://chaos.social/tags/format" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>format</span></a>, but in striving for that it introduces so much <a href="https://chaos.social/tags/complexity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>complexity</span></a>, that I would argue it achieves the opposite result. <a href="https://chaos.social/tags/YAML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>YAML</span></a> is full of footguns and its friendliness is deceptive. In this post I want to demonstrate this through an example.«</p><p>🤬 <a href="https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ruudvanasseldonk.com/2023/01/1</span><span class="invisible">1/the-yaml-document-from-hell</span></a></p>
#yaml
4 posts4 participants0 posts today
#yaml should be called ranl: Randomly Added Newlines
Right now I’m working on a #Python project that reads a lot of data from #YAML files. The data is validated later in the process when additional information from other sources is available.
Yet there seems to be no easy way to annotate the YAML data with information from which source file/position it was read. The YAML loader has the information internally (in the YAML Node) but there seems to be no easy way to preserve this information. (1/2)
Replied in thread
@ricci my favorite #yaml fact is yaml is a superset of #json. Sometimes a json parser can parse yaml but often not. But a yaml parser can always parse json (unless of course the 1.2 json spec isn’t being followed because who needs to be strict about specs?!).
Maybe that’s why meaningful error messages for a yaml parser are difficult?
Replied in thread
Ⓥ
So I got this working, using a choose block as you suggested - and a YAML template block. It seems weird to me though that there doesn't seem to be ANY way of getting an Assist question to take some kind of action on an answer without programming it in YAML.
Yes, I know YAML is wonderful and everyone should want to be a programmer, but for an org stating they want to make more possible with the built in GUI, it seems odd to launch a major new end user feature and not even mention that there is no alternative to use it but YAML?! Even in the docs.
Why isn't there just an action chooser in each answer, with "Add sentence"? Why is putting an action to an answer 3 levels deep in the GUI+YAML?
People on the internet with #kubernetes knowledge and history. I try to understand #KYAML. I understand the reason why they opted for a new modified format, and I agree with that. The only thing I just can't see, why it's called KYAML and not KJSON.
When I check example, it looks more like YAML-ified #JSON and not JSON-ified #YAML. To my eyes it looks more JSON than YAML.
TIL that `dig` can do #yaml:
https://framapiaf.org/@pmevzek/115108361810352153
FramapiafPatrick Mevzek (@pmevzek@framapiaf.org)@jpmens@mastodon.social @antondollmaier@mastodon.social @subnetspider@bsd.cafe @jwildeboer@social.wildeboer.net `dig` is often shipped with bind or bind-utils package, and also has a `+yaml` option which makes downstream parsing easier and more deterministic.
Jetzt habe ich meine ganzen Stunden in #Obsidianmd mit #YAML versehen:
- Klasse
- Fach
- Niveau (Basis-/Leistungsfach)
- Schuljahr
- Einheit
Das hatte sich mir bisher noch nie erschlossen, warum ich dafür nicht einfach Tags nutze. Und dann kamen die Bases und ich glaube, mir ist gerade der Kopf geplatzt.
Jetzt wird noch eine Vorlage für den Unterricht gebastelt, damit ich das nicht im Alltag vergesse.
#FediLZ
Continued thread
I had a lot of "fun" writing the #yaml definition for #esphome . A LOT of "fun". 
Esphome isn't really meant to write complex behaviours like a #child #toy 's program. It's meant for IoT devices: lightbulbs, covers, sensors, devices with very simple behaviors. But it's very convenient as it manages on its own all the wifi stack and libraries stuff, and it provides some functionalities for free (in this case, the possibility to use the whole led strip as a single #RGB #light seamlessly integrated in #homeassistant ).
Is this an #hack ? Sure it is. But does it work? Hell, yeah!
Esphome isn't really meant to write complex behaviours like a #child #toy 's program. It's meant for IoT devices: lightbulbs, covers, sensors, devices with very simple behaviors. But it's very convenient as it manages on its own all the wifi stack and libraries stuff, and it provides some functionalities for free (in this case, the possibility to use the whole led strip as a single #RGB #light seamlessly integrated in #homeassistant ).
Is this an #hack ? Sure it is. But does it work? Hell, yeah!
tabs vs spaces, FLAMES
Replied in thread
| wörk 
@cinimodev @0_o7 @NaiP What can be easier than edit a #yaml file and do a #docker compose up -d 