What a rude reply.
I am very well aware of Wine, but user prestige777 asked if MS Office could be run in a virtual machine on a Nexus 7. I simply explained why it currently cannot, without making any comment about whether it would be the best way or not. I do not see how that information qualifies to be called "total nonsene" (sic).
Well, first, its not meant to be rude or anything, It is more likely that his question sounded like he is not aware of the possibility to use wine instead of virtual windows, but yes, I might have got it wrong. So, once more, sorry if I offended you. I simply understand that question as "I want MS Office on my tablet".
Furthermore, as your experience of Office under Wine is somewhat limited, I can tell you that Office 2010 did not run under Wine for at least a year after its release, until Wine was updated to be compatible. So people wanting to run Office 2010 on Linux distributions at that time had to do it in a virtual machine or not at all.
Ok, thanks for enlightenment, but that does actualy mean that NOW it can be run correctly without virtual Win, right? And yes, most new SW (especialy that wich are ment for new Win) can have trouble runing under wine at first, that is common fact.
And modern PCs with multi-TB disks, quad core CPUs and 12 or 16 GB of RAM can run multiple virtual machines without any trouble at all - "waste of system resources" is a complete non-issue.
And for this, well, if you have Nexus 7 tablet which can be compared to system tat you have just described, then OK, you can do that without any noticeable impact on you system and I am sorry that I mentioned this subject, but I would certainly not try it on MY nexus which (sadly) has only 1GB of RAM :crying:
That may be so, but Microsoft Office for x86 will never run under Wine on a Nexus 7, so that's not actually going to help. Or are you assuming Office for Windows RT will one day be released by Microsoft as a separate product? Personally I wouldn't bet on that.
Well, first, I heard that MS is going to release office for android soon, so there will be no need for that. Second, as wine stands for "windows emulator" there is no need for similir architecture, if wine is ported correctly, because it should interpret windows api only, not use window libraries (although it can do that, it would not work on nexus or any ARM, you are right in that, but that has nothing to do with wine). Ok, right, I can not show you working example (I do not have it flashed yet, but now I certainly am going to test it soon), but that is the point of "emulator".