Timeline for Memory usage of JavaScript string type with identical values
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 27, 2016 at 16:02 | comment | added | Robert Harvey | @JörgWMittag: I guess my point is that only software developers would see my "yes, Javascript does this" statement, and interpret it as a mandate. If most, or all, implementations do it, then Javascript most certainly does it. It may not do it on a train, it may not do it on a plane, but Javascript does exhibit this behavior in some form in all of its implementations. | |
| Jul 27, 2016 at 16:01 | comment | added | Jörg W Mittag | Personally, I believe the distinction between a language feature that is guaranteed by the language spec, and a private internal implementation detail of an implementation that may change any time without notice and may or may not exist on other implementations, and if it even exists at all may or may not behave the way you expect, is a big difference. Especially in JavaScript, where you have pretty much no control over the implementation that your code is going to run in. | |
| Jul 27, 2016 at 14:50 | comment | added | Robert Harvey | @JörgWMittag: Seems like a distinction without a difference. | |
| Jul 27, 2016 at 0:19 | comment | added | Jörg W Mittag | Nitpick: if it's an implementation detail and varies between different implementations, then, no JavaScript doesn't do it. Some JavaScript implementations may or may not do it to some degree or other, but there is no guarantee. This is like saying that "Java does TCO, it's an implementation detail, and it varies between different implementations, but yes, Java does it." | |
| Jul 26, 2016 at 17:34 | vote | accept | Fredrik | ||
| Jul 26, 2016 at 16:24 | history | edited | Robert Harvey | CC BY-SA 3.0 |
added 209 characters in body
|
| Jul 26, 2016 at 16:14 | history | answered | Robert Harvey | CC BY-SA 3.0 |