develwoutacause’s Twitter Archive

12 results for BXPB

1. develwoutacause’s Twitter Archive—№ 139

   I can't really envision a team which would choose #BXPB, use it over a couple years, and still be happy with the library then. I feel that anyone who would

2. develwoutacause’s Twitter Archive—№ 127

   in the web space, is quite lacking right now. Improving #BXPB developer experience would mostly involve trying to improve #ProtocolBuffers developer experience as a whole. In particular:

3. develwoutacause’s Twitter Archive—№ 143

   #Comlink is a much better solution to this problem than #BXPB. It doesn't require an IDL and it's a simple library with no compiler or other funky requirements.

4. develwoutacause’s Twitter Archive—№ 135

   The only meaningful features #BXPB gets out of protocol buffers is the serialization format and existing semantics (such as how a service is defined, how RPCs are defined, request/response messages,

5. develwoutacause’s Twitter Archive—№ 116

   The project was called #BXPB - "Browser eXtension Protocol Buffers" (I know, I'm bad names). https://github.com/dgp1130/bxpb. github.com/dgp1130/bxpb This was a library intended to solve a common problem I've encountered a