@Paul%20Jolly, me likey! There's a really clean tokenizer implementation,
and if nothing else that's really nice baseline to mimic!
On Sunday, April 10, 2022 at 5:36:18 AM UTC-5 Andrew Pillar wrote:
> > I think there are two big advantages to making your application
> > consume either plain JSON
> I think there are two big advantages to making your application
> consume either plain JSON or YAML configs:
> 1. Everyone is familiar with them
> 2. You can use a more advanced tool like cue or jsonnet to generate
> them
I can see why people would prefer JSON, and I think it's fine for
storing
Cue (and jsonnet) come into their own when building large systems built out
of multiple components; they can create configs for multiple applications
derived from a shared top-level configuration. However, the applications
themselves don't have to understand cue or jsonnet, since both those can
> Out of interest, have you come across CUE?
>
I have heard of it, but not explored it in depth. At a glance it seems
too heavyweight for what I wanted.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop rec
Out of interest, have you come across CUE?
https://cuelang.org/
On Sat, 9 Apr 2022, 15:31 Andrew Pillar, wrote:
> An article I wrote about a new configuration library I developed in Go
> for working with structured configuration.
>
> Article:
>
> https://andrewpillar.com/programming/2022/04/09/
An article I wrote about a new configuration library I developed in Go
for working with structured configuration.
Article:
https://andrewpillar.com/programming/2022/04/09/structured-configuration-in-go/
Repo: https://github.com/andrewpillar/config
--
You received this message because you are sub
