global-fossil-fuel-supply-chain VS strictyaml

> Gasoline is an absolute miracle fuel.

Yes, it is a 'miracle' fuel, if you ignore these factors:

(a) Global oil, gas, and coal supply chains. The resulting complex network has 6.09mn nodes and 15.70mn edges: https://github.com/Lkruitwagen/global-fossil-fuel-supply-cha.... And the defense budgets of all the countries protecting these assets and supply lines.

(b) Trillions of dollars in subsidies every year: https://www.bloomberg.com/opinion/articles/2023-10-16/climat...

(c) 10 million air pollution deaths/year: https://www.nytimes.com/2022/07/08/opinion/environment/air-p...

> yes - wouldn't it be lovely to see governments uninvolved in these sorts of market decisions?

I agree. It should start with stopping all fossil fuel subsidies, 7 trillions/year and growing. And ethanol subsides, subsidizing ethanol production on 40m acres, just in US.

And have fossil fuel companies pay for their own military to protect their 6 million assets and 16 million transportation flows[2]. It should be determined by the companies themselves (free market) if these are worth protection, instead of having Govts protect these worldwide. Solar, on the other hand, will not require there protections, it does not depend on the exploration, extraction, shipping, processing, burning, waste output of any fuel. Solar is distributed, on every roof and field, nearly impossible for anyone to invade and destroy.

[1] Global Fossil Fuel Subsidies Reached $7 Trillion in 2022, an All-Time High: https://e360.yale.edu/digest/fossil-fuel-subsidies-2022

[2] https://github.com/Lkruitwagen/global-fossil-fuel-supply-cha...

Asset-Level Transition Risk in the Global Coal, Oil, and Gas Supply Chains\ (3 comments)

NestedText already is the way I use YAML; everything is intepreted as a string. I have some trust in my YAML parser to not mangle most strings. I could use NestedText, but users would be unfamiliar with it, and IIRC the only parsers are in Python. But then I could use StrictYaml too https://github.com/crdoconnor/strictyaml

you can stick to a subset of YAML syntax (e.g. strictYAML)

YAML stands for "YAML Ain’t Markup Language" - this is known as a recursive acronym. YAML is often used for writing configuration files. It’s human readable, easy to understand and can be used with other programming languages. Although YAML is commonly used in many disciplines, it has received criticism on the amoutn of whitespace .yml files have, difficulty in editing, and complexity of the standard. Despite the criticism, properly using YAML ensures that you can reproduce the results of a project and makes sure that the virtual environment packages play nicely with system packages. (If you're looking for another way to share environments there are other alternatives to YAML which include StrictYAML (a type-safe YAML parser) and NestedText)

The example you linked provides this as an example of a YAML document that he wants his format to support.

That safe subset exists and is implemented in a number of languages. It is called strict-yaml: https://hitchdev.com/strictyaml/

StrictYAML\ (33 comments)

To me those are in the category of "nice to have", and the problem is that every developer has different preferences for these [1] [2]. But the main features of StrictYaml, like supporting comments and less syntactic noise, I think are pretty uncontroversial, and perhaps it's worth it to get people to switch over for those alone. It doesn't need to be perfect, it just needs to be a significant enough improvement over JSON, and I'd say those two features are more than enough

[1]: https://github.com/crdoconnor/strictyaml/issues/37

[2]: https://github.com/crdoconnor/strictyaml/issues/38