Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
This is your friend autocorrect, did you mean pyson?
nlohmann::json
If you needs templating you can use jsonnet: https://jsonnet.org/ if you need scheme constraints you can use JSON-SCHEME: https://json-schema.org/ That is the whole design you add on what you need for your specific requirements. This gets back to the core philosophy of the Unix way vs something like JEE. The Unix way, is that you add on the functionality you need via pluggable parts as you need them. The JEE way is the same as the Angular way, the same as any other opinionated way, and that is trust us that we made all the right decisions for you, and it is rarely the case. A JSON based information transport solution with jsonnet bolted on top of it if you need templating, is far more robust than YAML. Because when you don't need templating you can just treat it as simple JSON.
If you needs templating you can use jsonnet: https://jsonnet.org/ if you need scheme constraints you can use JSON-SCHEME: https://json-schema.org/ That is the whole design you add on what you need for your specific requirements. This gets back to the core philosophy of the Unix way vs something like JEE. The Unix way, is that you add on the functionality you need via pluggable parts as you need them. The JEE way is the same as the Angular way, the same as any other opinionated way, and that is trust us that we made all the right decisions for you, and it is rarely the case. A JSON based information transport solution with jsonnet bolted on top of it if you need templating, is far more robust than YAML. Because when you don't need templating you can just treat it as simple JSON.