hjson-js VS skylark

Compare hjson-js vs skylark and see what are their differences.

skylark

Skylark in Go: the Skylark configuration language, implemented in Go [MOVED to go.starlark.net] (by google)
Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
hjson-js skylark
9 1
404 1,184
0.5% -
0.0 0.0
2 months ago about 5 years ago
JavaScript Go
MIT License BSD 3-clause "New" or "Revised" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

hjson-js

Posts with mentions or reviews of hjson-js. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-07-06.

skylark

Posts with mentions or reviews of skylark. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-08-14.
  • YAML and Configuration Files
    12 projects | news.ycombinator.com | 14 Aug 2021
    My stance is that YAML is a good format for configuration management and generation -- it's wonderful at filling gaps as your deployment model increases in complexity to provide a mechanism to "render" your configuration -- much like Skylark [1] does (derived from Google's internal GCL).

    YAML ends up being a powerfully declarative model [2] for the state of a data structure, rather than a straight representation, ironically often enough being used in turn for an imperative model like in Ansible [3]. Definitely friendlier than JSON. But personally, I really like YAML because it lets me compose using a traits/mixins-like model using & and , which allows for verbose, structured configuration inputs but concise configuration files.

    docker-compose YAML files extension fields [4], imo, are a great example of this type of model in action. When you leave this much pre-deserialization flexibility in your configuration representation, it makes building cool stuff like docker-compose ECS support x-aws- extension keys [5] and other plugin system-type capabilities much more straightforward than, for example, adding a new language feature to HCL.

    [1]: https://github.com/google/skylark

What are some alternatives?

When comparing hjson-js and skylark you can also consider the following projects:

Lowdb - Simple and fast JSON database

yaml-rust - A pure rust YAML implementation.

json5 - JSON5 — JSON for Humans

libyaml - Canonical source repository for LibYAML

Knex - A query builder for PostgreSQL, MySQL, CockroachDB, SQL Server, SQLite3 and Oracle, designed to be flexible, portable, and fun to use.

ytt - YAML templating tool that works on YAML structure instead of text

NeDB - The JavaScript Database, for Node.js, nw.js, electron and the browser

cue - The home of the CUE language! Validate and define text-based and dynamic configuration

buckets - A complete, fully tested and documented data structure library written in pure JavaScript.

schemapack - Create a schema object to encode/decode your JSON in to a compact byte buffer with no overhead.

strictyaml - Type-safe YAML parser and validator.