Show HN: Tired of the non-portability of my playlists, I wrote my own format

Re:Show HN: Tired of the non-portability of my playlists, I ... by hammerandtongs on Wednesday March 01, 2017 @12:58PM (#13766332)

Pretty printed json isn't too bad, but I intentionally never bulk edit it. This format shouldn't end up heavily nested anyway?

Toml is nice for simple configs/Cargo.toml but I think everything I said basically applies to it as well. Toml has recent work on it in 2017 for some (but not broad) library support but what does it look like in 2024?

[ Parent | on HN ]

Re:Show HN: Tired of the non-portability of my playlists, I ... by masklinn on Wednesday March 01, 2017 @01:36PM (#13766745)

> I think everything I said basically applies to it as well.

TOML is a much simpler format than YAML, and is a dialect/formalisation of INI files which have yet to go out of style. Direct database storage seems like a red herring (why would you want to store a playlist as a json blob?), so does "trivial JS consumption of the file".

[0] the entire spec is 10 pages, and that's with lots of examples, YAML 1.2 is ~80 pages

[ Parent | on HN ]

Re:Show HN: Tired of the non-portability of my playlists, I ... by StavrosK on Wednesday March 01, 2017 @01:15PM (#13766538)

Yeah, good point (plus it's not fantastic for this project anyway). I'm going to think hard on this, I quite like YAML...

[ Parent | on HN ]

Re:Show HN: Tired of the non-portability of my playlists, I ... by hammerandtongs on Wednesday March 01, 2017 @01:29PM (#13766682)

Fwiw I like yaml as well but it's just got a few too many issues these days.

While you are thinking maybe look at this

https://stedolan.github.io/jq/

and how people could leverage it when using your format.

[ Parent | on HN ]

Re:Show HN: Tired of the non-portability of my playlists, I ... by StavrosK on Friday March 03, 2017 @08:30AM (#13782691)

Ah yes, I know about jq, it's fantastic. I've switched to JSON, with heavy heart, but YAML seems too big indeed.

[ Parent | on HN ]