@dorianmuthig @Firefox @Chrome THAT DOESN'T WORK EITHER. X = close the app, shut it down, quit fucking wasting my memory. HONOR IT
-
-
Replying to @attritionorg
@attritionorg@Firefox@Chrome No, that's not what it means, it never did. Also, you can't "waste" memory. If you don't need it for ...1 reply 0 retweets 0 likes -
Replying to @dorianmuthig
@dorianmuthig@Firefox@Chrome X meant 'close the app' for a long time. an app can waste memory. these are simple truths.2 replies 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg You can take memory from being available to something else. "Free memory" is wasted memory. App memory is not free memory.1 reply 0 retweets 0 likes -
Replying to @dorianmuthig
@dorianmuthig are you trolling me? because seriously...1 reply 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg No, I am not. I am telling you something you appear not to understand about memory management.1 reply 0 retweets 0 likes -
Replying to @dorianmuthig
@dorianmuthig Yes, you are. You are talking 'last few/several years', in dev world, not user world. Your use of 'never' is just wrong.1 reply 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg In terms you can understand: The developer documentation for@Windows has never called for the X button to terminate a process3 replies 0 retweets 0 likes -
Replying to @dorianmuthig
@dorianmuthig a browser that takes 400k to operate one day, and 2.3 gigs the next day for the same operation, is *wasting* memory.2 replies 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg Do you otherwise use those 2.3 gigabytes of memory? If not, then it doesn't matter. Even if technically it's a memory leak bug2 replies 0 retweets 0 likes
@dorianmuthig when it takes 10x longer to do an operation one day vs the next, i don't care about your pedantry. USER vs DEV
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.