noyaml
go-sqlite
noyaml | go-sqlite | |
---|---|---|
9 | 12 | |
416 | 682 | |
- | - | |
5.3 | 7.5 | |
2 months ago | 8 days ago | |
CSS | Go | |
GNU Affero General Public License v3.0 | ISC License |
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.
noyaml
-
Kubernetes Through the Developer's Perspective
Most commonly written in YAML, these files are large and complex to read and understand. And being written in YAML comes with its challenges (and quirks) since it is an additional programming language that devs need to learn.
-
JSON Canvas – An open file format for infinite canvas data
YAML is kind of like C++:
> You like C++ because you're only using 20% of it. And that's fine, everyone only uses 20% of C++, the problem is that everyone uses a different 20% :)
https://eli.thegreenplace.net/2009/10/17/the-c-bashing-seaso...
The YAML footguns are too numerous to reproduce here, so here are some sources:
https://stackoverflow.com/questions/3790454/how-do-i-break-a...
https://www.arp242.net/yaml-config.html
https://noyaml.com/
-
Why the fuck are we templating YAML? (2019)
Relevant: https://noyaml.com/
YAML and its ecosystem is full of footguns and ergonomics problems, especially when the length of the document extends beyond the height of a user's editor or viewport. Loss of context with indentation, non-compliant or unsafe parsers, and strange boolean handling to name a few.
It becomes even worse when people decide that static YAML data files should have variable substitution or control flow via templating. "Stringly-typed programming" if you will. If we all started writing JSON text templates I think a lot of people would rightly argue we should write small stdlib-only programs in Python, Typescript, or Ruby to emit this JSON instead of using templated text files. Then it becomes apparent that the YAML template isn't a static data file at all, but part of a program which emits YAML as output. We're already exposing people to basic programming if we're using YAML templates. People brew a special kind of YAML-templated devops hell using tools like Kustomize and Helm, each of which are "just YAML" but are full of idiosyncracies and tool-specific behaviour which make the use of YAML almost coincidental rather than a necessity.
Yes, sometimes people would prefer to look at YAML instead of JSON, in which case I suggest you use a YAML serialization library, or pipe output into a tool like `yq` so you can view the pretty output. In a pinch you could even output JSON and then feed it through a YAML formatter.
The Kubernetes community seems to have this penetrating "oh, it's just YAML" philosophy which means we get mediocre DSLs in "just YAML" which actually encode a lot of nuanced and unintuitive behaviour which varies from tool to tool.
Look at kyverno, for examle: it uses _parentheses_ in YAML key names to change the semantics of security policies! https://kyverno.io/docs/writing-policies/validate/ . This is different to what I think is the (much better ideas of) something like kubewarden, gatekeeper, or jspolicy, which allow engineers to write their policies in anything that compiles to WASM, OPA, and Typescript/Javascript respectively.
We engineers, as a discipline, have decades of know-how building and using general purpose programming languages with type checkers, linters, packaging systems, and other tools, but we throw them all away as soon as YAML comes along. It's time to put the stringified YAML templates away and engage in the ecosystem of mature tools we already to use to perform one simple task they are already good at: dumping JSON on stdout.
Let's move the control flow back into the tool and out of the YAML.
-
YAML's homepage is displayed in YAML
The webpage documenting some of the sharp edges of yaml is also displayed as an editable yaml document
https://noyaml.com/
-
stopDoingJson
It’s the least secure config format, even worse than XML IMO since it’s unsafe even with trusted inputs. https://noyaml.com/
- That's a Lot of YAML
go-sqlite
-
JSON Canvas – An open file format for infinite canvas data
Check out https://github.com/zombiezen/go-sqlite if you're interested in trying out Sqlite in Go again. Nice interface, negligible compile time impact, fast, compiles without CGO. It's very comfortable.
I agree that going from text to sqlite is a bit of a hurdle, especially if you're not writing C :)
-
Jsonfile: A Quick Hack for Tinkering
struggling figuring out how to make my cgo sqlite cross-compile to Windows
Plenty of people trying to fix that.
There's at least:
https://modernc.org/sqlite
Then there's https://github.com/zombiezen/go-sqlite that actually builds https://crawshaw.io/sqlite on top of modernc.
And there's mine that has both a low level and a database/sql driver builds and runs everywhere Go does: https://github.com/ncruces/go-sqlite3
-
Any Full Text Search library for json data?
There are several different Go bindings for SQLite. I maintain https://pkg.go.dev/zombiezen.com/go/sqlite
-
What’s your preferred setup to work with SQL DB (without ORM) ?
I like and use https://github.com/zombiezen/go-sqlite for CGo-free SQLite. It avoids some of the problems database/sql has, discussed here: https://crawshaw.io/blog/go-and-sqlite.
- SQLite in Go, with and Without Cgo
- A pure Go embedded SQL database
-
Containerize Go and SQLite with Docker – 9MB Image Size
> C libraries are required to interact with SQLite
Or: modernc.org/sqlite (https://github.com/zombiezen/go-sqlite), "an automatically generated translation of the original C source code of SQLite into Go"
- Gokrazy – A Native Go Userland
-
Library for sqlite3 recommendations?
https://pkg.go.dev/modernc.org/sqlite via https://pkg.go.dev/zombiezen.com/go/sqlite
-
New advanced, CGo-free SQLite package
modernc.org/sqlite provides a database/sql driver, but does not (currently) provide an easy way to get at the more advanced functionality of SQLite, like streaming blob I/O or user-defined functions. David Crawshaw has argued that the database/sql API is not a good fit for SQLite, which is how crawshaw.io/sqlite came about.
What are some alternatives?
yj - CLI - Convert between YAML, TOML, JSON, and HCL. Preserves map order.
go-sqlite3 - sqlite3 driver for go using database/sql
hjson - Hjson, a user interface for JSON
bbolt - An embedded key/value database for Go.
doximus - static, smart and developer friendly API documentation generator
distroless - 🥑 Language focused docker images, minus the operating system.
json2jsii - Generates jsii-compatible structs from JSON schemas
bun - SQL-first Golang ORM
PyYAML
bun - Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
crd-to-sample-yaml - Generate a sample YAML file from a CRD
sqlite - Go SQLite3 driver