|
|
|
|
|
by BeetleB
2516 days ago
|
|
>because no one cares about that use case, and the resources wasted on making it possible are better spent on supporting the things that photographers expect cameras to do. No one except all the people who are using smartphones instead of DSLR's, causing a decline in sales? And what do you mean "no one cares"? The use case I've provided are precisely ones that "real" photographers care about. The amateur non-hobbyist photographer isn't going to want to do stacking on photos. The serious hobbyist/professional is. CHDK and Magic Lantern are great. My problem is that I don't use a Canon :-) But even if I did, I assume these are all unofficial? The idea is for the manufacturer to have official APIs. Now of course, it does make it more likely one will reduce the lifetime of a camera with a poorly written plugin (e.g. one that wildly keeps using the focusing motors), but they can simply say the warranty is voided if you install custom firmware/plugins. |
|
(I don't shoot Canon either, and yes, the homebrew firmwares are homebrew and thus not officially supported. I don't really know what effect they have on the warranty, but based on things I've heard, I think people just reflash bodies with stock firmware before shipping to the service center and it's basically fine.)
It's also worth noting that smartphones and ILCs don't compete directly any more. They never really did; once smartphones with good enough cameras to take casual snapshots and family photos started happening, ILCs were done in that market. Since then, they've been specializing toward those markets where they don't have to compete against smartphones. You're more or less suggesting that they do the opposite, and I don't know if you realize that the reason they're not already doing that is because they got murdered the last time they tried it and they're not in a hurry to get murdered again.