Timeline for Why is Global State so Evil?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 21, 2016 at 11:15 | history | wiki removed | yannis | ||
| Mar 22, 2014 at 13:40 | comment | added | luke1985 | @MadaraUchiha No, this argument is not shaky in any way. That are objective facts, unless some VM or other compiled language does some hardcore code optimisation with this kind of issue. Otherwise it's still relevant. Even with server side programms which use to be "one shot" the memory is reserved through the time of execution. With a high load servers this may be a critical point. | |
| Mar 22, 2014 at 13:28 | comment | added | Madara's Ghost | That's highly dependant on the language. In languages where programs run persistently, it may be true that you're able to save memory by using global space and singletons instead of instantiating many classes, but even that argument is shaky. It's all about priorities. In languages like PHP (which is run once per request, and objects don't persist), even that argument is moot. | |
| S Mar 22, 2014 at 12:51 | history | answered | luke1985 | CC BY-SA 3.0 | |
| S Mar 22, 2014 at 12:51 | history | made wiki | Post Made Community Wiki by luke1985 |