11–20 of 36 posts
why do we keep reinventing the wheel and not use asn.1?
The spec is too big, and it's too hard to implement correctly (let alone efficiently).
protobuf, swift, etc happened when an advertising company thinks it is an engineering company
why do we keep reinventing the wheel and not use asn.1?
Yes, asn.1 is the all signing, all dancing serialization framework. Protobuf's aren't. That isn't by accident.
Earlier quoted context omitted.
The spec is too big, and it's too hard to implement correctly (let alone efficiently).
you are using it all the time without realizing it. http://www.marben-products.com/asn.1/market.html protobuf, swift, etc happened when an advertising company thinks it is an engineering company
When I search the web for information about asn.1, I find very little that is of practical use. What library should I use? Why should I use it? How does it benchmark in comparison to the other tools? I've seen a few asn.1 library webpages and they all seem to take it as a given that I'm just looking for some way to deal with asn.1 data. They don't bother to try to convince me that their tool is efficient, or even that asn.1 is the right choice for my data in the first place.
Earlier quoted context omitted.
you are using it all the time without realizing it. http://www.marben-products.com/asn.1/market.html protobuf, swift, etc happened when an advertising company thinks it is an engineering company
Perhaps they should do more marketing, because speaking as a C++ developer: I picked between protobufs, flatbuffers and capt'n proto because they were easy to use, had active communities, and they had websites which explained how and why I should use their compiler/library/protocol. When I search the web for information about asn.1, I find very little that is of practical use. What library should I use? Why should I…
if you are curious here is a good blog post https://ttsiodras.github.io/asn1.html
i am working with asn.1 the protocol MMS
why do we keep reinventing the wheel and not use asn.1?
Earlier quoted context omitted.
The spec is too big, and it's too hard to implement correctly (let alone efficiently).
you are using it all the time without realizing it. http://www.marben-products.com/asn.1/market.html protobuf, swift, etc happened when an advertising company thinks it is an engineering company
Integers being encoded as signed is a nightmare for cryptography, which makes no use of them.
It would be really nice if there was a pure Python implementation that didn't use tons of unnecessary metaprogramming.
Earlier quoted context omitted.
Perhaps they should do more marketing, because speaking as a C++ developer: I picked between protobufs, flatbuffers and capt'n proto because they were easy to use, had active communities, and they had websites which explained how and why I should use their compiler/library/protocol. When I search the web for information about asn.1, I find very little that is of practical use. What library should I use? Why should I…
you are dismissing an old and proven technology because you feel it is not marketing to you effectively, which is the backend to the global telecom system (ss7) for the past two decades? why is this a movement in computer science to throw out old things that work? this is confusing to me like nosql. but "good marketing" is something that is called cap'n proto, sounds like a joke? if you are curious here is a good blo…