this post was submitted on 08 Dec 2023
81 points (97.6% liked)

Programming

16971 readers
161 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
all 17 comments
sorted by: hot top controversial new old
[–] [email protected] 34 points 9 months ago (1 children)

Q: Why didn't you write this in $NEW_LANGUAGE instead of crufty C++? A: I probably should have! $NEW_LANGUAGE is deservedly attracting a lot of attention for its combination of safety, readable syntax, and support for modern programming paradigms. I've been trying out $NEW_LANGUAGE and want to write more code in it. But for this I chose C++ because it's supported on all platforms, lots of people know how to use it, and it still supports high-level abstractions (unlike C.)

Lol

[–] [email protected] 12 points 9 months ago* (last edited 9 months ago) (1 children)

As someone who clicked partly to check if it was Rust-based, I think that's a 100% fair call-out lol

[–] [email protected] 4 points 9 months ago
[–] [email protected] 10 points 9 months ago

What's the difference between this and CBOR?

[–] [email protected] 8 points 9 months ago (4 children)

The main question I would have is why use it instead of protobuf? Having native support for binary values aside.

[–] [email protected] 8 points 9 months ago (1 children)

I'd love to see benchmarks testing the two, and out of curiosity also including compressed JSON docs to take into account the impact of payload volume.

Nevertheless, I think there are two major features that differentiate protobuff and fleece, which are:

  • fleece is implemented as an appendable data structure, which might open the door to some usages,
  • protobuf supports more data types than the ones supported by JSON, which may be a good or bad thing depending on the perspective.

In the end, if the world survived with XML for so long, I'd guess we can live with minor gains just as easily.

[–] [email protected] 2 points 9 months ago (1 children)

"Appendable" seems like a positive spin on the "truncated YAML-file is frighteningly often valid" problem...

[–] [email protected] 1 points 9 months ago

"Appendable” seems like a positive spin on the (...)

I don't think your take makes sense. It's a write-only data structure which supports incremental changes. By design it tracks state and versioning. You can squash it if you'd like but others might see value in it.

[–] [email protected] 0 points 9 months ago

It's not serialized from what I understand so it doesn't need parsing. It's sort of a structure+pointer dump. We'll see how well that translates to other languages than C though.

[–] [email protected] 6 points 9 months ago

Q: Why the name "Fleece"?

A: It's a reference to the mythical Golden Fleece, the treasure sought by Jason [emphasis mine] and the Argonauts.

I see what you did there...

[–] [email protected] 4 points 9 months ago (1 children)

Interesting. A year ago I was looking for something exactly like this for distributing data between multiple servers. Everything required a ton of overhead or was too big to use. I ended up just using json. I did discover that Brotli can compress 3 gigs of json down into just 70 megs nearly instantly.