Release milestones, compatibility progress and project updates.
A q database is only as useful as the languages that can reach it. This week we took the client libraries people already use with kdb+, pointed each at PeachQ, recorded what happened, and wrote it up. Five more languages now have a complete, recorded article: C#, Node.js, Go, Rust, and R through embedR.
The best test of q compatibility is other people's code: frameworks, client libraries and extensions written for kdb+. Since 0.77, a lot of that code now loads on PeachQ.
PeachQ 0.81 is out. Two features carry this release: enumerations are now a real datatype rather than something the engine resolves away, and there is a CSV reader that will tell you what it found instead of guessing.
PeachQ 0.77 is out. This release is about what happens in front of you: a help
system you reach with a single ?, a REPL that starts in modern mode with
autosuggest, and clearer failure when a script goes wrong.
Underneath, qSQL gains real select[n] and select distinct, files can be
appended to without a rewrite, and function values (projections, compositions
and derived functions) now travel over the kdb+ wire in both directions.
PeachQ 0.74 is out. This release adds live views, makes namespaces real q values, deepens functional qSQL support and improves compatibility across functions, arithmetic, IPC and the parser.
The milestone that matters most, though, is what those pieces make possible: PeachQ can now load and run qunit, the q unit-testing framework.
peachq v0.43 shipped eleven days ago. Three releases later we're at v0.66, and since the version number tracks our q conformance headline, that's the short version of the changelog: 43% → 66%.
Today I'm excited to announce PeachQ: an open-source implementation of the q programming language.
PeachQ is about more than building a runtime. We're building an open ecosystem.
The documentation and news you are reading live at peachq-org/peachq-website and accept pull requests.