ytklx
Re:The CUE Data Constraint Language
on Friday July 05, 2019 @03:15PM (#20365035)
Shameless plug: A JSON-like configuration language with considerably less features, no magic and no ambiguity: https://github.com/yuce/jacl
Re:Just Another Configuration Language
on Sunday June 30, 2019 @02:38PM (#20319689)
I've checked out Dhall very superficially, but it seems to be aimed at being a strict language to generate YAML and JSON, so IMO it has different goals than Jacl. E.g., an empty list is [] : List Natural in Dhall vs [] in Jacl. Dhall has A LOT of features. It looks more like a programming language than a configuration language. Since its goals are different, Dhall lacks a few features of Jacl like optional commas and underscore support in numbers. etc.
Re:Just Another Configuration Language
on Sunday June 30, 2019 @01:53PM (#20319455)
I am fed up with config languages where indentation matters or which require strange syntax to support a few levels of nested maps or require a manual to write a few lines of config.
I was dreaming of a config language which is as simple as JSON but also has a few niceties so it's not a pain to read/write it. This is what I came up with.
The golang implementation of the language is here: https://github.com/yuce/go-jacl The language grammar is in ANTLR4, so it should be easy to add support for other languages.
Hopefully this is useful to someone else.
Re:Pilosa: An open source, distributed index
on Friday May 31, 2019 @09:27AM (#20060635)
Roaring bitmaps is quite good at compressing bits. Just as an example: Say, most monkeys have the same number of bananas. Pilosa doesn't store it as MonkeyCount bits, but just a few bytes.
Re:Pilosa: An open source, distributed index
on Friday May 31, 2019 @09:04AM (#20060467)
This is very similar to how Pilosa saves integers. https://www.pilosa.com/docs/latest/data-model/#bsi-range-enc...
Re:Pilosa: An open source, distributed index
on Friday May 31, 2019 @09:02AM (#20060449)
Pilosa uses roaring bitmaps to store the data. Roaring bitmaps are compressed and performing bit operations on them is very efficient since they don't require uncompressing the whole bitmap to perform bit operations.