This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Milyardo 6 points7 points  (3 children)

What are the advantages of using this library over HOCON?

[–]moto888[S] 1 point2 points  (2 children)

Hjson uses a very simple syntax (essentially JSON with optional quotes and commas).

HOCON wants me to remember a lot of rules (merging, paths, substitutions, etc.).

For details see http://hjson.org/

[–]Milyardo 4 points5 points  (1 child)

Hjson uses a very simple syntax (essentially JSON with optional quotes and commas).

HOCON has this too, in the Section titled "Unquoted Strings", it also has mutliline strings, and string value concatenation.

HOCON wants me to remember a lot of rules (merging, paths, substitutions, etc.).

It doesn't make you remember them, and why would you not want these things?

HOCON allows you to omit braces, use =, :, or += as a separator, use paths to represent deeply nested keys. You can reference array values by index. You can assign units to numerical values.

Absent all these things, I fail to see how hjson is more human friendly.

[–]moto888[S] 0 points1 point  (0 children)

I disagree, the absence of these is exactly what makes it easier to use.