I developed it because I was tired of writing custom binary parsers for network protocols and wanted to create an easy-to-use tool directly from format experts without the need for developer support - while ensuring adequate performance. Ideal for centralising message encoding/decoding operations in different formats.
('Try it' section - it comes with a working example using CAN as format)
The goal is to easily convert binary data to JSON and vice versa, using only a JSON configuration file that describes the message format.
The main value is to eliminate the need to write code for each binary format you need to support. Instead, you just define the structure of the message in a config file and the engine handles the rest. This could be particularly useful for those working with various legacy or embedded systems protocols.
A single Bixit engine can decode multiple formats simultaneously. The advantages in terms of manageability are significant, as to update a format or add new ones, you simply need to move a configuration file, without having to recompile anything.
maxmosca•6mo ago
('Try it' section - it comes with a working example using CAN as format)
The goal is to easily convert binary data to JSON and vice versa, using only a JSON configuration file that describes the message format.
The main value is to eliminate the need to write code for each binary format you need to support. Instead, you just define the structure of the message in a config file and the engine handles the rest. This could be particularly useful for those working with various legacy or embedded systems protocols.
A single Bixit engine can decode multiple formats simultaneously. The advantages in terms of manageability are significant, as to update a format or add new ones, you simply need to move a configuration file, without having to recompile anything.
I'm looking for sincere feedback on this idea.