You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
In fact, *reading* is a destructive operation in RAM. Reading one byte means reading 64K (which destroys it), then writing back the 64K untouched! However, the RAM chips perform this read-write operation when directed, so the 64K doesn't have to go out via the bus and back. (2/n)
The difference is that RAM doesn't wear out, so nobody cares that it works this way. The RAM can also combine a long sequence of reads or writes, sequential or scattered, within one page, into one read, a sequence of I/Os, and a write back to the array. (3/n)
So next time someone tells you "RAM can be accessed at a granularity of one bit", remember that's not really true. It actually uses huge pages just like Flash, which is fundamental when memory is organized as a big 2D array (the page size is one dimension). (4/4)
Addendum: I meant 64 kibibits (64 Kibits or 64Kib) in my original tweet, not 64 kibibytes. It's usually something like 8 bits per chip × 8 chips = 64 bits for a whole DIMM, and pages (rows) are 1024 addresses within each bank, so 65536 bits.
It's also nearly always handled for you in hardware so developers rarely need to care. Flash needs manual read, erase, write on nearly everything.
Only to the extent that "dumb" Flash controllers still exist. Modern Flash controllers will do read/erase/write/FTL for you much like DRAM controllers will open and close rows for you.
Of course it wears out. If you don't refresh the data will be gone pretty fast. :)
The RAM itself doesn't wear out. The data is another matter ;)
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
