When the difference is two bytes of code...
A bit here, a byte there, and sure, why not just make the 5DIII a 1D X in a smaller form factor and charge half the price. Hell, that 61 point AF should be in the next Rebel camera, and why not throw in a FF sensor, too.
Here's how it works. Canon makes design decisions, sometimes informed by customer needs/wants, sometimes independent of them. Canon builds cameras and markets them. A miniscule minority of people whine and prattle on about how this feature isn't what they wanted or that feature should have been implemented like this. A vast, overwhelming majority of people buy what is, for all intents and purposes, an excellent camera with many significant improvements relative to it's predecessor. Astoundingly enough, that overwhelming majority of buyers frequently includes many of the whiners, and most of that minority of complainers that didn't buy the camera had no intention of doing so in the first place. Canon makes a profit. The shareholders are happy. Canon teams pat themselves on the back, and start designing the next body which will implement even more incremental improvements, and generate the unavoidable and practically meaningless whining the next time around, unless said malcontents have in the meantime gone over to Apple Discussions to bitch about the new iPad.
Aye, I agree, being able to set minimum aperture would be extremely handy when you need a thicker DOF. I'm curious...does ANY camera, ANY brand, do that?
Yes. On the 1DIV and 1DsIII, C.Fn I-13 is "Set aperture value range" and allows you to specify a smallest value between f/91-1.4 and a largest value between f/1.0-64. (<whine>damn canon sucks what if I need to set an f/stop range from f/76-91, but the smallest max aperture I can set is f/64 this feature is USELESS even though I didn't know it existed before reading this thread, but for sure I'm never
buying that crippled 1-series body now</whine>).
I presume the 1D X will have similar functionality.