So now that the ‘new’ framework is officially deprecated and what will follow to it in the future is said to be ‘compatible’ to the classic framework: would I rather use the classic framework for any JSON work or the ‘new’ one, which is considerably faster when it comes to JSON handling?
What would you do?
Last year I did a new JSON project with classic framework, since classic was/is fast enough for generating big JSON files.
Also with classic JSON implementation is quite straight forward.
Never endorsed the new framework and only use it at places where it’s really beneficial to do so.
I use JSONItem_MTC by @Kem Tekinay
https://github.com/ktekinay/JSONItem_MTC
It’s a drop-in replacement for the native JSONItem. It emulates all its features but should perform certain functions faster.
Classic JSONItem is really fast in a series of tests it often performed better than a dictionary.
And it was what brought me back to the old framework instead of the Xojo framework often because you cannot use Text as values. I mean you can, but you render the toString property useless by that. TypeCasting all Text variables back to String was boring, so I would recommend the classic framework for JSON anyway.
Isnt JASON implementation in the New FrameWork better than Classic ?
If so, I bet they will use that code in the future Framework 2.0" 
[quote=389163:@Dirk Cleenwerck]I use JSONItem_MTC by @Kem Tekinay
https://github.com/ktekinay/JSONItem_MTC
It’s a drop-in replacement for the native JSONItem. It emulates all its features but should perform certain functions faster.[/quote]
It also fixes some bugs that, I believe, still exist in the native JSONItem.