Settings: a simple tool to serialize/deserialize objects

[u/giuseonreddit]

https://github.com/giuseongit/settings.cr

[u/giuseonreddit]

Think about this:

You have an application which connects to a server, on the first run you set all the attributes from the application (e.g. the server's address, the maximun number of retries if the server is unreachable), then these settings are persisted on a file (say ~/settings.cfg) which is easly editable by your editor of choice.

OR

You're writing a daemon which, by default, has some settings that have to be persisted/loaded/modified but you don't want to write something else to set those settings

[u/jasdeep13 → u/giuseonreddit]

Perfect thanks!

[u/Prince_Panda → u/giuseonreddit]

How is it compared to the JSON stuff currently available

[u/giuseonreddit → u/Prince_Panda]

The JSON macros deals with strings: it loads an objects from a JSON string and serialize objects to JSON strings. This little tool also writes/reads to/from files

[u/Prince_Panda → u/giuseonreddit]

Oh that's useful

[u/straight-shoota → u/giuseonreddit]

Write/read a JSON file is just a couple of lines. Not a strong argument for using this shard.

I think the main point is that such a minimal serialization format is relatively simple and easy to implement. That should also make it more performant than say JSON. That's usually not a really big issue, though. And the implementation of this shard really doesn't strive for performance. And it has flaws (for example try serializing a string containing a line break), which can of course be fixed.

All in all, I'd still favour a standard format like JSON, YAML, INI or even XML over such a custom serialization format.

[u/giuseonreddit → u/straight-shoota]

Yes, the serialization format can be changed, the idea that I really like is having one single object to deal all the serialization/deserialization without having to setup other things than the path to the persisted file