-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add tXml to benchmark #1
Comments
Thanks for the heads up @strarsis. A good parser creates an object where any value can be accessed directly (dot notation) without loops and iterative searches. I cannot do a fair comparison because All five libraries in this test create an object where any child can be accessed directly by key, and they are configurable in a way so that they are compatible drop-in replacements for each other. With For E.g. in stead of this
The target object should follow the common structure:
If that's done and it's still fast, it becomes a helluva lot more useful. 💯 |
@Redsandro: Thanks for your test! |
@strarsis I had a quick look, but I can't use it in that way. Perhaps if @TobiasNickel would be interested in adding the options to write the object in a way similar to the other libraries. |
@Redsandro: That's great! What I like about that library is that it is native JS (and its speed claim, well, to be tested). |
Just found a new, maintained XML parser in native JavaScript: https://github.com/TobiasNickel/tXml
Would be interesting to know!
The text was updated successfully, but these errors were encountered: