go-toml
edn
go-toml | edn | |
---|---|---|
2 | 34 | |
1,636 | 2,567 | |
- | 0.7% | |
7.4 | 0.0 | |
5 days ago | over 2 years ago | |
Go | ||
GNU General Public License v3.0 or later | - |
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.
go-toml
-
What Is Wrong with TOML?
I wrote one of the Go implementations [0] when TOML was announced and have maintained it since.
As a library implementor, I wish arrays would hold only one type at a time, but I get that could be useful for users. But as a user, I wish tables were fully defined once (more can't be added up later in the file), especially when using larger files.
[0]: https://github.com/pelletier/go-toml
-
Hw to open these files locally using vs code?
Looks like a it's struggling to install a go dependency, something prob changed since the time this project was made and now. I don't use go but someone more familiar with it can prob help you. Googling the error brought me to this it might solve your problem https://github.com/pelletier/go-toml/discussions/562
edn
-
Apple releases Pkl – onfiguration as code language
> was utterly surprised how no one ever apparently has thought to create a configuration/templating system that's basically a fancy library on top of Scheme.
There's Clojure's extensible data notation: https://github.com/edn-format/edn
- Why the fuck are we templating YAML? (2019)
-
I made a basic python client and ORM for XTDB
A thin language layer around edn/datalog, the query language
-
What Is Wrong with TOML?
EDN (Extensible Data Notation) is a subset of Clojure: https://github.com/edn-format/edn
It is:
- Streamable
- Extensible
- Whitespace-insensitive, but there are formatting conventions for readability
-
The real reason JSON has no comments
To begin with, EDN is somewhat like the JSON of Clojure. And regarding the code is data/data is code nature of Clojure, it is Clojure. It doesn't have some of the vagaries of JSON, and it is also extensible.
-
Ron: Rusty Object Notation
Alien is not a reason something is bad, just that's it's unusual. JSON was a bit alien when it first arrived as well, as everyone was used to XML at the time.
`{num 5, val 4}` looks fine to me, but we can do even better! We already know objects/maps are always in pairs, so we don't really need that comma either. Just do `{num 5 val 4}` and we save yet another unnecessary characters.
Of course, I didn't come up with this format myself, what I actually want JSON to be is EDN (https://github.com/edn-format/edn) which is a standalone format but also directly used in Clojure, so it already exists inside a programming language and works very well. There keys are strings though, so you example would end up being `{"num" 5 "val" 5 "person" var}`, where commas are optional.
-
JSON vs. XML with Douglas Crockford
I just checked out the spec, and it gets pretty ugly in the Table section. A lot of the json examples are both shorter and IMO more precise. Stuff that’s not allowed with [table] is allowed with [[table]], and it’s confusing to understand what level of depth I’m at.
I’ll take edn over any of “em. https://github.com/edn-format/edn
-
Taming the Time: how to install & develop with XTDB
As XT is written in Clojure and it natively supports Clojure’s data types, we were not satisfied with available JSON types and decided to give EDN a try - that way we would have way more supported types:
-
Design patterns are a solution to the problem OOP itself creates
Compare the nightmare that is pickling with how simple it is to serialize pure data with edn in clojure. What ends up happening is people passing around JSONs or whatever and writing parsing/encoding code at each end, which makes things unnecessarily more complex, and dangerous, and error prone, and boring, etc...
- The YAML Document from Hell
What are some alternatives?
viper - Go configuration with fangs
json - JSON for Modern C++
hocon - go implementation of lightbend's HOCON configuration library https://github.com/lightbend/config
EPOE-Forked - Github repository for EPOE-Forked
ini - Package ini provides INI file read and write functionality in Go
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
toml - Instream TOML to JSON encoder
yamllint - A linter for YAML files.
env - A simple and zero-dependencies library to parse environment variables into structs
dhall-lang - Maintainable configuration files
go-ini - Go package that encodes and decodes INI-files
json - A tested JSON parser / serializer