C++ is at least backwards compatible (for 99% of code anyway, yes I know about some features being removed, but that’s an exception and not the rule).
C++ is at least backwards compatible (for 99% of code anyway, yes I know about some features being removed, but that’s an exception and not the rule).
Trucy would be trying her hardest to get him to buy this
Shame that PES/WE not only got renamed to eFootball, but also sufferred from the post-Kojima PTSD at Konami.
It recently caught up to DDR and it’s slowly catching up to Yu-Gi-Oh as well (if it didn’t already).
MTG poops and Yugipoops never get old
BOUNS ROUND
hur hur hur
NYOOM
I’m surprised nobody thought of the demoscene twisters
TRUXTON
EDF EDF EDF
Ahh the memories
I got banned from “World News @ lemmy.ml”
Gee, what else is new?
I’m referring to the philosophy behind the usage of said allocated ram.
If you allocate 5 cookie jars to store 1 cookie in each jar, then that’s not good.
If you store 2 cookies per jar, that’s better already, but still kind of crap.
If the websites keep putting rocks in those jars, then you’ll obviously run rampant with usage. (Read: https://tonsky.me/blog/js-bloat/ )
The goal is to store as many cookies in least amount of jars. You might crumble them down and reconstruct them later (compression and/or clever code) but that could take more brain (processing) power (of which we kinda have, especially on the desktop).
As you’ve said, it’s often a tradeoff between processing power and memory usage and depending on the application, you can configure things the way you need them (at least when you’re coding it).
It’s specifically about the efficiency of the usage. If it’s not used effectively, then it really is a waste.
And we all know how efficient the Web is nowadays…
Chart