Comment on Introducing Pkl, a programming language for configuration

itsathursday@lemmy.world ⁨9⁩ ⁨months⁩ ago

• abhibeckert@lemmy.world ⁨9⁩ ⁨months⁩ ago

  Json is a nightmare to write.

  Compare this pkl code:

  host: String
  port: UInt16(this > 1000)
  

  To the equivalent in json-schema:

  {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "host": {
        "type": "string"
      },
      "port": {
        "type": "number",
        "minimum": 1000,
        "exclusiveMinimum": true
      }
    },
    "required": ["host", "port"]
  }
  

  I think it’s pretty clear pkl is better.

  source

  • itsathursday@lemmy.world ⁨9⁩ ⁨months⁩ ago

    Nice

    source
• canpolat@programming.dev ⁨9⁩ ⁨months⁩ ago

  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.

  source

  • Lynxtickler@sopuli.xyz ⁨9⁩ ⁨months⁩ ago

    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?

    source

    • TerrorBite@meow.social ⁨9⁩ ⁨months⁩ ago

      It's the other way around. The YAML schema supports JSON because YAML was designed as a superset of JSON.

      @Lynxtickler @canpolat

      source

      • Lynxtickler@sopuli.xyz ⁨9⁩ ⁨months⁩ ago

        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.

        source
    • canpolat@programming.dev ⁨9⁩ ⁨months⁩ ago

      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.

      source