Oldfeller--FSO
Serious Thumper ModSquad
   
Offline

Hobby is now "concentrated neuropany"
Posts: 12686
Fayetteville, NC
Gender:
|
Why is Google working on a new OS that is intended for "FAST processors that utilize non-trivial amounts of memory"?
Intel processors actually haven't gotten much faster at all for years now, but the ARM processors certainly have gotten MUCH FASTER in the meantime. Apple and Qualcomm have an ongoing competition for processor/graphics speed -- with the octa-core A-72/A-53 Kirin from Haewai and the big Deca cores from Mediatek both moving up mightily on the traditional speed leaders.
ARM has been sold now to a banking consortium out of Japan, so we expect some changes to come from the now Apple-less controlled ARM. Apple orchestrated things pretty completely, and insisted that ARM hold back their progress so Apple could milk each new ARM design level in turn, yes, that Apple shite that should end now.
Some of the Consortium members have been demanding better processing speed and much better GRAPHICS GRAPHICS GRAPHICS out of ARM for several years now. Now they may get just that.
Google sees CHANGE coming, with very fast systems type memory measured in 10's of gigabytes available on all mobile devices. We see the first wave of this memory shipping right now, and it won't be hyper expensive for very long at all as you have 2-3 sources coming on line right now.
We see both Huawei /Kirin and Mediatek forcing the current generations of ARM right up to the upper edges of its designs and asking for MORE, please !!!!
=======================================
Fuchsia is still in its early stages. Google has it up and running on an Acer Switch Alpha 12, a laptop-tablet hybrid, but apparently also wants to get it running on a Raspberry Pi, a much less powerful machine. It also runs on devices powered by ARM chips, the type that powers almost all phones and tablets.
Fuchsia team
Some notable developers are contributing to the project. Among them:
Travis Geiselbrecht, who worked on a failed but influential operating system from the 1990s called BeOS, the iPhone and the OS for the Danger Hiptop operating system, which T-Mobile sold as the original Sidekick. Brian Swetland, who worked on BeOS, the Hiptop OS and who spent many years toiling on the core parts of Android. Chris McKillop, a member of the original iPhone team and the original WebOS team who also worked on the QNX operating system used in cars and some BlackBerry devices. He also worked on the Danger Hiptop. Adam Barth, a longtime member of Google's Chrome team who more recently has been working on a Google tool designed called Flutter to make it easier for programmers to write software that runs on Android and iOS. He also built an operating system of his own called Tau.
This is a team picked for succeeding in past attempts to "redo the whole thing" as that seems to be a part of Fuchsia's bottom to top intentions.
This may be an attempt to ditch the inherent limitations of Java and several other traditional Linux/MS designs such as Flash, which have been tweeked to do multi core processors but still there is a strong need for a clean sheet of paper concerning what is going to be happening pretty soon.
Google gets that. Design an OS to run cleanly on what is coming ..... ditch the historical legacy stuff if need be. Design for a new type of OS that lives naturally in a 100+ gigabyte fast live systems memory space, in other words. Where graphics speed is the real functioning limitation, not processor or memory access or anything else.
Design something that by nature is VR ready, in other words .....
ARM will move in concert, using the capabilities exposed by the new OS and new fast memory space to make their processor generations and associated hardware fit the new capabilities better and better.
|