A bit off topic but notice you have a golang version of your JSON parser lib as well.
Is there any specific strategy you follow WRT building JSON parsers that you found lacking in std lib implementations in order consider writing your own?
Quite curious re: the reasoning behind writing the libs and how you even figured it was worth the time effort to consider it in first place.
It actually started with XML. At the time there were not any decent options so I wrote my own and then made it a C extension. JSON can next since XML worked out so well. Basically JSON parsers were slow and I thought I could do better.
It started out as just a need for better performance than the standards but with golang I felt a full implementation of JSONPath would be of benefit to myself and others.
The real motivation though is the challenge and knowing people are using the code I write.
Comments
A bit off topic but notice you have a golang version of your JSON parser lib as well.
Is there any specific strategy you follow WRT building JSON parsers that you found lacking in std lib implementations in order consider writing your own?
Quite curious re: the reasoning behind writing the libs and how you even figured it was worth the time effort to consider it in first place.
Impressive performance numbers in general :)
It actually started with XML. At the time there were not any decent options so I wrote my own and then made it a C extension. JSON can next since XML worked out so well. Basically JSON parsers were slow and I thought I could do better.
It started out as just a need for better performance than the standards but with golang I felt a full implementation of JSONPath would be of benefit to myself and others.
The real motivation though is the challenge and knowing people are using the code I write.