Date: Sat, 23 Aug 2025 00:29:42 +0300 From: Vadim Goncharov <vadimnuclight@gmail.com> To: "Poul-Henning Kamp" <phk@phk.freebsd.dk> Cc: David Chisnall <theraven@FreeBSD.org>, Konstantin Belousov <kostikbel@gmail.com>, hackers@freebsd.org Subject: Re: My experiences with Rust Message-ID: <20250823002942.305119b2@nuclight.lan> In-Reply-To: <202508221937.57MJbBtK008806@critter.freebsd.dk> References: <aKiWZ1I3pqZSOsfk@kib.kiev.ua> <202508221712.57MHCPDl008201@critter.freebsd.dk> <E04D6E14-8EA1-446B-8C9C-762C9956F6D5@FreeBSD.org> <20250822214848.25569826@nuclight.lan> <202508221937.57MJbBtK008806@critter.freebsd.dk>
index | next in thread | previous in thread | raw e-mail
On Fri, 22 Aug 2025 19:37:11 +0000 "Poul-Henning Kamp" <phk@phk.freebsd.dk> wrote: > -------- > Vadim Goncharov writes: > > > Why it should be reinvented-wheel-bicycle "nvlist" instead of CBOR, RFC > > 8949 > > Because CBOR is just another kind of binary data structure, and we are > trying to get away from that ? We are trying to get away from ad hoc binary "C structures", not from "binary" per se. It's XXI century, text only formats are not sifficient now. > Any format you cannot open in a text-editor is by definition a non-starter. No. Any format you could not *securely parse* in kernel is by definition a non-starter. And minimal CBOR codec (e.g. queue(3)-based) takes just several hundreds of C code where it is hard to get security errors - no text format parser in kernel can ever compare to this. And nobody needs to open "format" *directly* in text editor - as CBOR is seamlessly converted to/from text-form EDN (extended diagnostic notation, a superset of JSON), that sounds like a requirement to open ELF binary directly in text editor instead of just putting (dis)assembler into pipeline. -- WBR, @nuclighthelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20250823002942.305119b2>