Date: Tue, 26 Aug 2025 14:19:23 +0300 From: Sulev-Madis Silber <freebsd-hackers-freebsd-org952@ketas.si.pri.ee> To: freebsd-hackers@freebsd.org Subject: Re: CBOR (Was: My experiences with Rust) Message-ID: <07588255-8B19-44FD-BDDB-A3A0F7D5A324@ketas.si.pri.ee> In-Reply-To: <20250826115714.67bca22b@nuclight.lan> 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> <20250823002942.305119b2@nuclight.lan> <202508222133.57MLXtAA009189@critter.freebsd.dk> <20250823073225.ecf498cc3e7a6dcb68ccc3c8@dec.sakura.ne.jp> <1614139543.20250823141311@yahoo.com> <A56F576C-6748-47E1-91AA-8A33D20DFD19@blackskyresearch.net> <277027377.20250825132929@yahoo.com> <EFD5963A-347F-4DCB-9EAB-34A43AD59764@blackskyresearch.net> <20250825213703.0570107f@nuclight.lan> <E5D68219-CCC4-4D74-B3E9-17AC092F4068@ketas.si.pri.ee> <20250826115714.67bca22b@nuclight.lan>
index | next in thread | previous in thread | raw e-mail
On August 26, 2025 11:57:14 AM GMT+03:00, Vadim Goncharov <vadimnuclight@gmail.com> wrote: >On Tue, 26 Aug 2025 05:09:46 +0300 >Sulev-Madis Silber <freebsd-hackers-freebsd-org952@ketas.si.pri.ee> wrote: > >> when i finger the old sw and hw, same patterns appear. things could use >> binary. things could be secured with deprecated methods. both will lead to >> loss of access. your conversion program could get lost. what if in future, >> my current favorite, json is also outdated and in same position of xml. but >> those things you could at least read and parse with your own eyes. sure, at >> some point the efficiency will maybe lead to binary formats but this is at >> loss of use in future. i bet if we still have people messing with data in >> future, i can already hear them yelling who was that asshole that created >> all this. since it's usage loss, it's even easy to forget it was for some >> greater good. even compression algorithms fail. ever had that feeling, phew, >> at least this thing uses *TEXT*. i can read it with standard tools? even if >> the output sucks balls. at least it's understandable. unsure if this >> justifies text only outputs but be prepared that somebody either discards or >> just curses a lot on your binary formats as much as you and i do now. the >> problem is in extra tools you need to invent to read all. yeah one could >> argue that maybe even ascii text is special binary format, we just still >> have tools to "get" it. but that thing has at least lasted for so long. >> along with c programming language and so on. why did they last? nothing >> really bad lasts. so maybe it was good? maybe people found it >> understandable? i have no idea how future will be. but some of those things >> are older than me and i can still understand them. why? it's all plain >> text!!! that one we view as bad and inefficient and what not. it all doesn't >> matter if you can't parse it > >Your wall of something looking like ASCII text is completely unreadable. Could >you rewrite it into something more understandable / structured? > well, no, actually. i often look at paragraphs in others and don't know how they split them. i never knew. but i bet you can still parse it with some tools. i bet you could maybe find similar docs too somewhere. where noone else overlooked it. but it's still better than binary? if it were something machine readable. unsure, maybe "| tr '[:punct:]' '\n'"? i don't have honest idea how to write. i recall school didn't teach the formatting stuff either or i wasn't able to get. in either way, i don't knowhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?07588255-8B19-44FD-BDDB-A3A0F7D5A324>