this post was submitted on 03 Feb 2024
36 points (97.4% liked)
Programming
17669 readers
162 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I just learned about Pkl, so take this with a grain of salt. JSON Schema and Pkl seem to have some overlap. But JSON schema is not specifically designed for handling configuration and Pkl supports other formats like YAML.
JSON schema supports YAML as well, no? That's because JSON and YAML are both essentially just different syntaxes for writing the same objects right?
It's the other way around. The YAML schema supports JSON because YAML was designed as a superset of JSON.
@Lynxtickler @canpolat
I get where you're coming from, but JSON Schema still absolutely is the framework that supports YAML files and not the other way around. I've been using JSON Schema pretty heavily lately to write schemas using YAML, for validating YAML.
@Lynxtickler ahh, I misunderstood what you were referring to. Didn't realise you were talking about JSON Schema and not the JSON syntax itself.
Possibly. My point is: despite having a common subset Pkl and JSON schema doesn't seem to be solving the same problems. But, I'm just learning about it, so I may just be wrong.