AND there is a point to make that some devices just doesn’t have the RAM, disk space, or processing power necessary to run a Windows application. The latter implies that Android does not have some key components, like OpenGL, to run some Windows applications. The former implies that our support isn’t good enough, yet. It will run a very limited number of Windows applications (some because they just aren’t supported yet on Android and some because Android doesn’t / won’t support them at this time). And yet, here we are…Īllow me to clearly state that like the first Model T’s and the very first light bulbs, CrossOver Android is far from perfect. It’s like Henry Ford building a car for a population that didn’t have roads or Thomas Edison creating a light bulb for a population that didn’t have electricity. At best, they were building a hypothetical solution to prove that it could be possible to run Windows based applications on an Intel Android device. Our development team essentially built a solution for a problem that could not be solved or fixed. There were no Intel based laptops or clamshells. When this development started, there were no Intel based tablets.
Think about this…When this development started, there were few, if any, Intel based phones. Over the past two years, nine months, two weeks and a day, the product has changed and changed and changed again all in the hopes of somehow being useful on Android devices. At by this time tomorrow, CodeWeavers will release the Tech Preview of CrossOver Android to the select users who signed up for initial access. It’s taken us two years, nine months, two weeks, and a day to get to this point in the process. FINALLY!!!! We have arrived at the cusp of Androidism.
0 kommentar(er)
