You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why are we building yet another project that supports all CRC algorithms? Are we just adding another CRC crate? The problem is that all these CRC implementations are maintained by different people at different levels, providing different APIs and depending on different crates. All of this combined makes the CRC ecosystem a mess. We either have to rely on a crate that hasn't been released in seven years or one that has a hard dependency on cbindgen which doesn't make sense at all.
Don't get me wrong, I respect all their maintenance and effort; I just want to fix them our way—the fast way.
Fast Labs is an open organization that welcomes any interested maintainers to join. It was created by friends who share similar visions and is not controlled by any business entity.
All CRC implementations will share the same core (if possible), the same dependencies, provide the similiar API, and will be maintained by the same group.
Fast Labs will strive to communicate quickly, build efficiently, and release promptly. You won’t have to wait three years for your patch releases.
Fast Labs will advance v1.0 while ready, ensuring that your applications no longer need to rely on 10 different versions of CRC implementations simultaneously.
The text was updated successfully, but these errors were encountered:
There are so many CRC crates available in the Rust ecosystem:
Why are we building yet another project that supports all CRC algorithms? Are we just adding another CRC crate? The problem is that all these CRC implementations are maintained by different people at different levels, providing different APIs and depending on different crates. All of this combined makes the CRC ecosystem a mess. We either have to rely on a crate that hasn't been released in seven years or one that has a hard dependency on
cbindgen
which doesn't make sense at all.Don't get me wrong, I respect all their maintenance and effort; I just want to fix them our way—the fast way.
v1.0
while ready, ensuring that your applications no longer need to rely on 10 different versions of CRC implementations simultaneously.The text was updated successfully, but these errors were encountered: