@Beatrix W 10 MB JSON? Is this really a good idea? And a test project would really help.
Yes. There are lots of objects to serialize. I don’t expect I could write a custom markup that I could parse faster, is version control friendly, and human readable. Plus, I can (and do) parse the documents in my PHP-based API, as well as having some PostgreSQL triggers able to act on the document data with relatively little code.
@ChristianSchmitz Still I would appreciate if you compare with our classes, too.
Just to know for me where I stand with them.
Yeah, as mentioned I was originally testing for my own project, but this experiment has grown a little bit, so I’ll include MBS in round 2.
@Kem T Thom, if you test compile with 64-bit Aggressive, you should find that JSONItem_MTC is significantly faster than what you posted in your blog. Parsing in my tests runs at about 0.5X the speed of the new framework. To be clear, the new framework stuff is still the fastest, but my code is significantly faster than JSONItem and much closer to the new framework.
I will run the next round in compiled mode, but my original logic is that any performance gained in JSONItem_MTC would also be gained by JSONItem since they’re both Xojo-based. So the overall outcome wouldn’t change. But yes, compiling will get us closer to an apples-to-apples comparison so I’ll do that.