Benchmarking demonstrates that V8 is the slowest way to parse JSON in a .NET application.
I created a benchmark to compare the performance of the JSON parser in V8 to the fastest third-party JSON Parser library (JSON.Net) and also one of the slower examples of the framework's built-in parsers (JavaScriptSerializer).
This is obviously purely a matter of personal curiousity, just for fun, and purely academic. I am not aware of any compelling practical applications for using V8 as a JSON parser in .NET applications. Somebody was bound to try it eventually. For example, I doubt a web application creating an instance of V8 for each request to moderately popular URL would keep running for very long.
I created a benchmark to compare the performance of the JSON parser in V8 to the fastest third-party JSON Parser library (JSON.Net) and also one of the slower examples of the framework's built-in parsers (JavaScriptSerializer).
This is obviously purely a matter of personal curiousity, just for fun, and purely academic. I am not aware of any compelling practical applications for using V8 as a JSON parser in .NET applications. Somebody was bound to try it eventually. For example, I doubt a web application creating an instance of V8 for each request to moderately popular URL would keep running for very long.
