Are you saying that the file system change isn't related to their use of NVRAM or that there are other solutions to battery protection of memory that you prefer?
If it's the latter, "nothing to do" is a bit too strong. I'd say that even if I didn't think button batteries have other issues - potential form factor growth, the cost to support Uncle Ed calling to deal with it, etc.
I was in tech support for a programming language compiler Long Ago, and it was difficult enough to explain to programmers that their CMOS batteries needed to be replaced.
It (FAT) is also one step towards their desired infrastructure for bigger internal memory capacities.
I think the Mossberg mention is a net negative. Anyone who reads him knows he likes the T600 and the take away is "the 650 is great for power users if they wait a while for the problems to be solved". I think there is a small niche of price insensitve, geek, early adopters who hear of the 650 from him and order, but I think the FUD resonates with a larger demographic.
Then again, in proofreading this before I hit post I replaced a "their" with a "there" and a "they're" with a "their" so this whole post may all be in excess of my baseline level of cluelessness. Or I have some sort of acoustic coupler kludge in my brain that needs to be cleaned, or even better replaced with SPDIF or something. The whole translation to phonetics / sound circuitry responsible for such errors has no business being in the thought->keyboard path. Hopefully that was fixed in the 1968+ models.
"If he were dying he wouldn't have bothered to carve 'aaaaaaaaaayyyyyyyyrrrrrrrrrggggggggggg' onto the wall!"
"Maybe he was dictating"
(MPaTHG)
Sorry for rambling... sleepy
