3 ms·

How did you get that Intel and Microsoft failed in mobile "markets" because they had backwards compatibility with 32-bit and 16-bit apps? (I'm thinking you migh

by vaxman 7y ago

How did you get that Intel and Microsoft failed in mobile "markets" because they had backwards compatibility with 32-bit and 16-bit apps? (I'm thinking you might not know the difference between RISC and CISC --hint: one is not better. than the other.) > So instead of using the die space saved by removing 32 bit support and using it for some combination of increasing performance, improving battery life, decreasing die size etc they should have left it and suffered? Removing the 32-bit instructions/registers isn't what achieves the performance and battery life improvements, those come from eliminating the RAM, cache-misses and context-switches dedicated to the 32-bit apps and that can be more than offset by not activating the 32-bit environment at all, unless it is actually needed by the user for legacy compatibility. > Apple was able to port their core OS to 128Mb RAM/400Mhz iPhone back in 2007 Note that MS ported their core to a 4Mb RAM 36MHz Velo-1 back in 1997 and many Chinese manufacturers make low power chips like that (for DVD players, TV sets, etc.) that ship with operating systems that have exactly the same APIs (knock offs) of Win16 and Win32. > 2007. Since then, they’ve ported it to everything from watches, tablets, and set top boxes. Microsoft has tried and failed in each of those markets. You might want to look into Xbox, Surface, Foldable Surface the old Casio watch and what kind of boat anchor Apple's Darwin has been for realtime embedded devices like Apple Watch.

scarface74 7y ago
How did you get that Intel and Microsoft failed in mobile "markets" because they had backwards compatibility with 32-bit and 16-bit apps? (I'm thinking you might not know the difference between RISC and CISC --hint: one is not better. than the other.) Apple was able to successfully port the Core of MacOS to phones and other products - MS not so much. I didn’t say anything about RISC vs CISC, but Intel has had to throw a lot more money at the x86 architecture to achieve performance while keeping backwards compatibility and they have not been able to make a chip that was suitable for mobile. Removing the 32-bit instructions/registers isn't what achieves the performance and battery life improvements, those come from eliminating the RAM, cache-misses and context-switches dedicated to the 32-bit apps and that can be more than offset by not activating the 32-bit environment at all, unless it is actually needed by the user for legacy compatibility. That’s also logically not true. How can it not be a win to being able to remove entire parts of the chip dedicated to 32 bit instructions? Note that MS ported their core to a 4Mb RAM 36MHz Velo-1 back in 1997 and many Chinese manufacturers make low power chips like that (for DVD players, TV sets, etc.) that ship with operating systems that have exactly the same APIs (knock offs) of Win16 and Win32. How did that work out in the market? Also in 1997, there was a lot less cruft in Windows than a decade later. And the XBox hasn’t exactly been a success in terms of either profitability or units shipped compared to mobile. Microsoft is busy fighting the last war. The “foldable surface” is vapor ware, the x86 based surface still has horrible performance and battery life compared to ARM tablets.

by vaxman 7y ago

scarface74 7y ago

How did you get that Intel and Microsoft failed in mobile "markets" because they had backwards compatibility with 32-bit and 16-bit apps? (I'm thinking you might not know the difference between RISC and CISC --hint: one is not better. than the other.) Apple was able to successfully port the Core of MacOS to phones and other products - MS not so much. I didn’t say anything about RISC vs CISC, but Intel has had to throw a lot more money at the x86 architecture to achieve performance while keeping backwards compatibility and they have not been able to make a chip that was suitable for mobile. Removing the 32-bit instructions/registers isn't what achieves the performance and battery life improvements, those come from eliminating the RAM, cache-misses and context-switches dedicated to the 32-bit apps and that can be more than offset by not activating the 32-bit environment at all, unless it is actually needed by the user for legacy compatibility. That’s also logically not true. How can it not be a win to being able to remove entire parts of the chip dedicated to 32 bit instructions? Note that MS ported their core to a 4Mb RAM 36MHz Velo-1 back in 1997 and many Chinese manufacturers make low power chips like that (for DVD players, TV sets, etc.) that ship with operating systems that have exactly the same APIs (knock offs) of Win16 and Win32. How did that work out in the market? Also in 1997, there was a lot less cruft in Windows than a decade later. And the XBox hasn’t exactly been a success in terms of either profitability or units shipped compared to mobile. Microsoft is busy fighting the last war. The “foldable surface” is vapor ware, the x86 based surface still has horrible performance and battery life compared to ARM tablets.