appsplit: "Sahas Katta is a true Android believer and enthusiast living in Santa Clara. He went down to the nearest Microsoft Store to participate in a competition called “Windows Phone Challenge”.
Long story short, He won the challenge fair and square but Microsoft reps denied him the prize. When asked for an explanation Microsoft employee replied with these two historic words “Just Because”"
Microsoft is laying off more employees, a new round after they cut thousands last year. It seems like many big tech companies are doing the same.
Google Reportedly Set to Launch Tool Revealing Battery Degradation Over Time for Phones and Tablets, Says Android Authority.
Amidst the AI frenzy of 2023, major players like Google, Microsoft, and Meta are in the spotlight, launching their own generative AI systems.
the Windows Phone had no chance at its own challenge.
Dont mess with the droids, you will get owned!!!
I understand but still Galaxy Nexus is way better optimized than any Windows Phone out there.
"To stir the pot more, Google’s Android expert Dianne Hackborn responded late Thursday nite: https://plus.google.com/105...
The reader who pointed this out to me wrote “In short, the intern got it wrong.” I don’t think it’s so cut and dried. I’ll try to summarize what Hackborn wrote: 1) It’s true that Android lacks a real-time thread just for screen rendering like iOS, says Hackborn. 2) Instead, Android lets apps be prioritized as default or background. UI threads normally run at default. Application processes running in the background are forced to run in the background. 3) Background threads collectively are only allowed to take up 10% CPU utilization maximum. 4) There was a ‘foreground’ priority in the original Android but it was abandoned b/c it turned out not to give enough priority to things like the UI. 5) Android uses the two sets of priority threads as part of its goal of creating a ‘sandbox’ architecture that separates all apps, incl. 3rd-party ones, for security reasons. This, says Hackborn, differs from iOS’s design which didn’t originally accommodate 3rd-party apps. 6) Setting up a separate thread just for drawing the UI in real-time would not have been worth it, due to a bunch of complex reasons Hackborn lists that I don’t quite understand. 7) Android only “recently” began to use hardware acceleration for drawing inside the UI. 8) That’s because hardware acceleration isn’t as simple as making your graphics chip handle the UI. It takes a lot of memory and multiple processes to manage the graphics chips as “most mobile GPUs still have fairly expensive GL context switching.” 9) Hackborn acknowledges that “there are of course many things that can be improved in Android today, just as there are many things that have been improved since 1.0. As other more pressing issues are addressed, and hardware capabilities improve and change, we continue to push the platform forward and make it better.” 10) But…it’s no technical piece of cake to enable your iOS app to support touch scrolling at a smooth 60 frames per second, either, says Hackborn, quoting a comment to that effect from an outside developer. “Based on this statement I don’t see any indication that there is something intrinsically flawed about Android in making lists scroll at 60fps, any more than there is in iOS.”
Good read...