问HN：在TS/JS中使用Protobuf，令人恐惧吗？
我想快速确认一下，因为这个生态系统让我感到担忧。
根据我所看到的，protobuf-es 在 API 和整体可用性方面显然是赢家。我还花了整整两天时间来解决一个通常偏差为 1 的解析错误： https://github.com/bufbuild/protobuf-es/pull/1183，这对生产环境产生了重大影响。如果该实现真如其所声称的那样合规，那么我对此表示担忧。
这次经历与我过去的经验一致——JavaScript 在这个生态系统中显得格格不入。我只是希望它不必如此。
查看原文
I'm asking for a quick, well, scream check, because the ecosystem concerns me.<p>From what I've seen, protobuf-es is the clear winner in terms of API and general usability. I also burnt two full days resolving an off-by-typically-1 parsing error: https://github.com/bufbuild/protobuf-es/pull/1183, which impacted production significantly. If that implementation is the most compliant as it claims, well, I have concerns.<p>This recent experience is consistent with my past experience - that JS is the oddball of the ecosystem. I'm just hoping it doesn't have to be.