Hey guys
Hey guys,
System.JSON.Readers and System.JSON.Writers were borrowed from the famous James Newton-King' Json.NET library, that is pretty amazing :D #10Seattle surprising me each day.
:D
System.JSON.Readers and System.JSON.Writers were borrowed from the famous James Newton-King' Json.NET library, that is pretty amazing :D #10Seattle surprising me each day.
:D
... if only it was fast and easy to work with! See http://www.delphitools.info/2012/09/17/spotlight-on-dwsjson/ and http://blog.synopse.info/post/json-benchmark-delphi-mormot-superobject-dwsjson-dbxjson
ReplyDeleteA. Bouchez that seems to compare DBXJson to other parsers. Is the System.JSON the same as DBXJson or did #10Seattle introduce new libraries? If so, these should then be re-compared to the other parsers and the results published.
ReplyDeleteCurrently we use SuperObject but I'm all for native components if they are up to scratch.
Rick Wheeler AFAIK #10Seattle has more or less the same version as the original DBXJson, but with the addition of a SAX-like approach, used for MongoDB. I did not test the SAX way, just the DOM way, which is very slow and resource consuming, even in Seattle.
ReplyDeleteAll those "native" units have evolved a lot, sometimes with breaking changes among versions. So if you have a project on a dedicated Delphi version, no problem. But if you want to support several Delphi versions (as we do for our framework), I would stay away from those units, since they are not stabilized.
A. Bouchez The implementation of System.JSON.Readers is highly based on James Newton-King's one. Assuming that the original JSON.NET library is the fastest JSON library for .NET, the Delphi RTL's one should be too :D
ReplyDeleteA. Bouchez thanks for the feedback. I'd agree that for commercial projects breaking changes are simply not acceptable every release so we'll stick with the SuperObject for now. It goes without saying that time is too precious to be spent on house keeping trivial matters such as JSON serialisation :-)
ReplyDelete