amesenbrink wrote:
As someone who's job is partially associated with firmware updates for consumer electronics, I would just like to say that updating firmware of any type is a nightmare.
Any change must be tested and retested in any number of ways. If an error is found it's a code change, and the test process restarts. The risks here are huge for a device like a camera, many people rely on the device to make a living. The backlash for a single mistake may not be worth the risk.
Firmware is generally limited to the physical memory set aside during design. Expanding that software is generally a function of finding ways to cut down the code required to provide the basic feature set offered when the product was delivered, then testing to make sure those changes didn't break anything. To add a new feature it must fit within the memory space allowed, provide new functionality without any physical change to the device, and again not break anything.
Then comes delivery of the new firmware. How does the update work? How difficult is the upgrade process for the casual user? What happens if power is lost during an update? How many calls will this update generate to customer service? What part of the customer base will actually get the new firmware? How many will be aware of the new features?
Firmware updates are a massive time sync, and a big risk. If the reward is not significant it is more worthwhile to have the engineers working on another part of the product line. The first questions asked are: Can we sell more of the product based on the new feature? Will this change reduce the money we spend on customer support?
Game consoles, and PC components, Smartphones and Tablets are designed with updates in mind. The marketplace the live in requires that they have the ability to adapt to changing needs. That flexibility doesn't exist in the camera market yet, I'm not sure it needs to.