115
Homarr - A modern and easy to use dashboard. 30+ integrations. 10K+ icons built in. Authentication out of the box. No YAML, drag and drop configuration. (homarr.dev)
submitted 1 year ago by to c/selfhosted@lemmy.world
29 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 36 points 1 year ago (16 children)

I use homepage and pretty happy with it. “Drag and drop configuration, no yaml” actually put me off.

  • permalink
  • fedilink
  • source
  • hideshow 16 child comments
    •
  • [–] 8 points 1 year ago (12 children)

    I wish we would all start switching over to JSON for configuration files. It's so much easier to parse, and you can't screw it up with too many spaces or not enough.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 12 child comments
    •
  • [–] 19 points 1 year ago (3 children)

    No thanks. Yaml isn't perfect but by God json is best used to return and parse data, not input it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 9 points 1 year ago* (2 children)

    My biggest peeve with JSON when I'm forced to use it as a configuration format is that it doesn't have any syntactical support for comments.

    So I can't even add any notes to the file.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago*

    Yea, this is a deal breaker imo. My code tends to be 10 to 1 comments to lines of code ratio. Configuration even more so.

    jsonc/json5 exists for this use case, but few tools actually use it, yaml is far more popular

  • permalink
  • fedilink
  • source
  • parent
  • [–] 10 points 1 year ago (2 children)

    No support for comments? Hard pass

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 1 year ago (1 child)

    Yeah, this is my biggest annoyance with JSON. As a data structure it's very elegant, but it only really makes sense to people who know how to code, and without the ability to add comments you have to rely heavily on external documentation to make it readable to most users.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 1 year ago

    And like yeah, both the wonderful (and foss!) .json5 and Microsoft's semi-proprietary(?) .jsonc exist, but most projects just use their language's default JSON parser that doesn't recognize them. What I would personally love to see is .json5 support baked into the default JSON parsing libraries of Python, Go, etc. (Enabled by a flag, likely.) It's a superset of regular JSON and fully ES2019 compatible, so there shouldn't be any issues.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 1 year ago (1 child)

    I used to think that until I figured out yaml and now yaml isn't so bad.

    It helps that text editors know what yaml is now so insert spaces when you hit tab etc

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 5 points 1 year ago

    My biggest gripe with yaml (especially in docker-compose files) is that l, for me at least, it is absolutely not clear when I need to add dahes (-) in front of multiple entries and when it's just linebreaks.
    And there are no easy accessible docker-compose validators...

  • permalink
  • fedilink
  • source
  • parent