Timeline for Is Node.js correct choice for JSON parsing and IO driven
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 3, 2013 at 23:29 | comment | added | Benjamin Gruenbaum | What I mean by extremely fast, is that in practice it is not a limiting factor. | |
| Jun 2, 2013 at 21:16 | comment | added | Esailija | What do you mean extremely fast? It is general purpose textual format, it's going to be much, much slower than custom binary formats usually used in database<->application comm. | |
| Jun 2, 2013 at 20:52 | comment | added | Benjamin Gruenbaum | I never said JavaScript has a distinct advantage in parsing JSON, or an advantage at all (It's not even in the "pros" section, or debated). All I claimed is that JS parses JSON extremely fast, not saying other languages do so slowly, not saying that's an advantage for JS, only that modern JS engines got to the point where serializing or de-serializing JSON is almost never an issue. | |
| Jun 2, 2013 at 20:16 | comment | added | Esailija | I don't see how Javascript has a distinct advantage in parsing JSON. First of all, JSON is not technically a subset in that line and paragraph separators (\u2028, u2029) are illegal in Javascript string literals but not in JSON string literals. Secondly, even if it was, I still don't see how the syntactic similarity could possibly affect performance. If it's because javascript has direct equivalents of JSON values, then, so do many other languages but it's still unrelated to syntactic similarity. | |
| Jun 2, 2013 at 17:43 | history | answered | Benjamin Gruenbaum | CC BY-SA 3.0 |