View Single Post
Old 11-10-2017, 03:02 PM   #232
barryem
Wizard
barryem ought to be getting tired of karma fortunes by now.barryem ought to be getting tired of karma fortunes by now.barryem ought to be getting tired of karma fortunes by now.barryem ought to be getting tired of karma fortunes by now.barryem ought to be getting tired of karma fortunes by now.barryem ought to be getting tired of karma fortunes by now.barryem ought to be getting tired of karma fortunes by now.barryem ought to be getting tired of karma fortunes by now.barryem ought to be getting tired of karma fortunes by now.barryem ought to be getting tired of karma fortunes by now.barryem ought to be getting tired of karma fortunes by now.
 
barryem's Avatar
 
Posts: 2,459
Karma: 68781975
Join Date: Oct 2012
Location: Arkansas
Device: Paperwhite 4
Quote:
Originally Posted by issybird View Post
The storage partition is frustrating. And, as so many have said, while 1 GB is enough for most uses, increasing the total memory on one hand but decreasing the amount available for sideloading seems needlessly in your face. It's really not going to force anyone to buy B&N content who ordinarily wouldn't, but it's going to put off (obviously, going by the reaction here) some who would have bought but don't like the restriction. One minor side plaint is that I would have asked/commented about the memory issue, but no one approached me the whole time I stood there playing with the new Nook. With one of the Nooks, didn't they do something where you could take it to the store and they'd repartition the memory for you to make more available? Is this total fantasy on my part?
You just made me think of another possible reason for the partitioned memory. Just a wild guess but being a know-it-all I must be right.

What if the source code from the old model was used for this thing, at least in part, and it was just easier to increase the partition size than to do away with the partitioning? If that's the case it's only there because it was cheaper to leave it than remove it.

In source code things like fixed sizes and minimum sizes are usually constants and changing them is simply a matter of changing a number in a text editor and recompiling. It's likely no change in logic would be needed, reducing the development and debugging time.

I really don't have the slightest reason to believe this is what happened but 35 years of programming tells me it might have happened.

Barry
barryem is offline   Reply With Quote