Timeline for JavaScript compilation in V8
Current License: CC BY-SA 3.0
Post Revisions
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:10 | history | edited | URL Rewriter Bot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| May 1, 2017 at 11:34 | comment | added | Jörg W Mittag | "Does it mean that JavaScript is not an interpreted language in V8?" – There is no such thing as an "interpreted language". A language is a language. Period. Interpretation and compilation are traits of an interpreter or compiler (duh!), not a language. | |
| Feb 21, 2017 at 14:23 | vote | accept | Boni García | ||
| Feb 16, 2017 at 13:39 | comment | added | T.J. Crowder | @UnholySheep: The wiki is out of date: v8project.blogspot.co.uk/2017/02/help-us-test-future-of-v8.html | |
| Feb 15, 2017 at 12:28 | answer | added | sheltond | timeline score: 5 | |
| Feb 13, 2017 at 14:54 | history | edited | Boni García | CC BY-SA 3.0 |
added 175 characters in body
|
| Feb 13, 2017 at 13:01 | review | Close votes | |||
| Feb 17, 2017 at 0:00 | |||||
| Feb 13, 2017 at 12:41 | comment | added | UnholySheep | From the wiki: "V8 compiles JavaScript source code directly into machine code when it is first executed. There are no intermediate byte codes, no interpreter." | |
| Feb 13, 2017 at 12:38 | history | asked | Boni García | CC BY-SA 3.0 |