4 ms·

I would love to here some MSFT people who work on the Net Core teams thoughts about these libraries, because it seems the community has really amazing things to

I would love to here some MSFT people who work on the Net Core teams thoughts about these libraries, because it seems the community has really amazing things to contribute, such as this string builder library. Net Core has seen amazing improvements compared to Framework, yet often still falls behind existing community offerings. e.g. UTF8JSon library: https://michaelscodingspot.com/the-battle-of-c-to-json-serializers-in-net-core-3/ https://michaelscodingspot.com/the-battle-of-c-to-json-seria... Outperforms the new Net Core json library. HyperLinq: https://medium.com/@antao.almada/netfabric-hyperlinq-zero-allocation-fe5d0dd6b1a6 https://medium.com/@antao.almada/netfabric-hyperlinq-zero-al... Is basically Linq with 0 allocations. What is blocking MS from integrating these approaches into Net Core?

apk-d 7y ago
There's usually trade-offs when it comes up to those highly optimized libraries. Utf8json doesn't have nearly as many features as more universal serializers. HyperLinq requires you to write boilerplate code for each custom collection you wish to support, and won't work on AOT platforms (such as Unity targeting the IL2CPP runtime, which happens to be the use case that would actually heavily benefit from such optimization).