JHa
First Officer
Flight distance : 99797 ft
Czechia
Offline
|
JodyB Posted at 12-13 23:36
It just seems to me that some folks are taking this to extreme. Really, by today's technological standards, there really shouldn't be a 32-bit version of anything (hardware or software wise). But given the way things are, it is what it is today. There are companies that are using 32-bit as a way to sell cheaper to it's consumers and that leads companies like Google to try and come up with a way to start a transition away from 32-bit. DJI is no exception. If they choose to never publish a 32-bit version of DJI Fly, that is there choice. They have to start somewhere and there will be upset customers. They expect and know it's going to happen. They are probably gauging the customer backlash with this very Mavic Mini project. While it is possible they may yet publish a 32-bit version and I hope that they change there mind and do, it is quite possible that they may not. They may stand there ground and say from this point forward, 64-bit is it. But one thing I wish they would do if they decide 64-bit is going to be the path, make a public statement as such. I'm not going to get on my soap box and preach one way or the other. I myself was a victim of this. I had three tablets that I was planning on using for my MM and couldn't because they were all three 32 bit so I understand all to well the consumer side of this topic. I also understand the business side of it as well.
If you want respect today's standards, you must respect whole ecosystem. You can't say, we have 64bit CPU, we build only 64bit sw, if today's standard on android is 32/64bit sw on 64bit hw and migration from 32bit to 64 bit is only in "you must add 64bit sw version for android 9 and later" phase. Yes, this is DJIs decision, but it is a mistake. |
|