inkeliz

karmem

Go2022–2022

inkeliz / karmem

karmem

Karmem is a fast binary serialization format, faster than Google Flatbuffers and optimized for TinyGo and WASM.

Web Development Data & Databases

Explore on GitHub Read Hacker News discussions

5Distinct people

5Mentions

1Explicit recommenders

685GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Karmem is a fast binary serialization format, faster than Google Flatbuffers and optimized for TinyGo and WASM.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

There one commit referencing my favorite data structure [1], the discriminated union (DU) / tagged union / enums with values: > kmparser: implement id generator > That is the…

infogulch used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week5 dated mentions

Observed mentions: 2022-05-17 13:32:53 UTC to 2022-08-01 13:31:51 UTC. Weeks start Monday, UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
May 16	2022-05-16 00:00:00 UTC	2022-05-23 00:00:00 UTC	1	0	1
May 23	2022-05-23 00:00:00 UTC	2022-05-30 00:00:00 UTC	0	0	0
May 30	2022-05-30 00:00:00 UTC	2022-06-06 00:00:00 UTC	0	0	0
Jun 6	2022-06-06 00:00:00 UTC	2022-06-13 00:00:00 UTC	1	1	0
Jun 13	2022-06-13 00:00:00 UTC	2022-06-20 00:00:00 UTC	0	0	0
Jun 20	2022-06-20 00:00:00 UTC	2022-06-27 00:00:00 UTC	0	0	0
Jun 27	2022-06-27 00:00:00 UTC	2022-07-04 00:00:00 UTC	0	0	0
Jul 4	2022-07-04 00:00:00 UTC	2022-07-11 00:00:00 UTC	0	0	0
Jul 11	2022-07-11 00:00:00 UTC	2022-07-18 00:00:00 UTC	0	0	0
Jul 18	2022-07-18 00:00:00 UTC	2022-07-25 00:00:00 UTC	0	0	0
Jul 25	2022-07-25 00:00:00 UTC	2022-08-01 00:00:00 UTC	0	0	0
Aug 1	2022-08-01 00:00:00 UTC	2022-08-08 00:00:00 UTC	3	1	2

What Hacker News says

5 sources

gizzlon·Aug 1, 2022

https://github.com/inkeliz/karmem#languages Languages Currently, we have focus on WebAssembly, and because of that those are the languages supported: AssemblyScript Golang/TinyGo ~Swift/SwiftWasm~ Zig C

In Karmem: A fast binary serialization format faster than Google Flatbuffers

infogulch·Aug 1, 2022Recommendation phrase

There one commit referencing my favorite data structure [1], the discriminated union (DU) / tagged union / enums with values: > kmparser: implement id generator > That is the first step to implement Unions/Interfaces, it's also useful to know what is the expected message type to decode. I don't see any other mention or plan about DU's in the repo or metadata. I'm curious what their position is on it. [1]: https://github.com/inkeliz/karmem/commit/626e6d3b380eb5236c9...

In Karmem: A fast binary serialization format faster than Google Flatbuffers

siddontang·Aug 1, 2022Submission

Karmem: A fast binary serialization format faster than Google Flatbuffers

157 points · Open discussion

ngaut·Jun 8, 2022Submission

Karmem: A binary serialization format even faster than Google Flatbuffers

2 points · Open discussion

adrianfcole·May 17, 2022

I'm a maintainer on wazero. We have two things in progress on debugability, though both are stalled as we complete the recently announced WebAssembly 2.0 draft spec (nearly done) [1]. 1. DWARF support - this requires those compiling to Wasm to configure to emit that. It is also murky because there's no canonical mapping in Wasm (most rely on LLVM underneath, but wazero is zero dependencies so we can't do that). Anyway, this is still on the table. [2] 2. Observability hooks - wazero is uniquely go-native which means we can do things like context propagation, allowing telemetry hooks including distributed tracing. While it may not seem intuitive to use that in Wasm, it can allow you to re-use tools that can show a trace graph. We have an experimental listener now, which has an example of how to make some strace looking logs. [3] Later, we'l

Read the rest

l convert this to an interceptor approach so that you can do metrics and stuff nicer. [4] Regardless of this, debugging is easier because everything is in go. Apart from the DWARF thing which is totally important, the runtime being in Go completely means you debug everything going on, down to what is allocating memory, just by putting break-points in Go code. This is a very neat thing, and has helped some folks develop better code. Ex. https://github.com/inkeliz/karmem Hope these help. Indeed the road to wasm is littered with a lot of runtimes, mostly abandoned or archived. We're hoping to buck the trend debugability, so watch the issues below if interested, and feel free to tell us anything we aren't doing right, too. [1]: https://github.com/tetratelabs/wazero/issues/484 [2]: https://github.com/tetratelabs/wazero/issues/58 [3]: https://github.com/tetratelabs/wazero/blob/main/experimental... [4]: https://github.com/tetratelabs/wazero/issues/451

In Wazero: The zero dependency WebAssembly runtime for Go developers