3 ms·
As far as .NET implementation goes, it is really bad: - Very old and currently obsolete project target - As a result, does not use modern data types such as S
by neonsunset 5y ago
As far as .NET implementation goes, it is really bad:
- Very old and currently obsolete project target
- As a result, does not use modern data types such as Span<T>
- No utilisation of ArrayPool<T> which is important for things like serialisers where you expect to deal with buffers a lot
- Appears to be a blind Java port given provided code style
This is not acceptable when working with low-level and binary structures which this standard is focused on.
Yes, I know, this is an OSS project and therefore instead of complaining here I should have been working on contributing a PR to fix those issues. However, my main concern is that this standard and set of libraries in the current form work against the performance-sensitive nature of working with binary data.
- tubs 5y agoThe cpp is also pretty bad as another comment points out. All sub structures end up being allocd pointers with no way to have them inlined as values.
- Jasper_ 5y agoThe JavaScript runtime isn't much better; it's missing support for 64-bit types using BigInt, and the runtime itself could be far more lightweight and efficient. I would submit fixes, but the project just seems unmaintained as a whole.
- deleted 5y ago[deleted]