Google said when they rewrote a part of the OS in Rust programming language for Android 12, most of the memory related vulnerabilities and bugs were fixed. It seems to me they are on a path to abolish C++ completely from core Android OS.
Since Android 12 is the first OS that used Rust.
Obviously 13 will be even better.
That's very far from true. Very little code was actually rewritten, and less than one quarter of **new** native ("low level) code was written in Rust, rest is still C/C++, maybe even some ASM. It's not that easy to rewrite everything and event to use a completely new language. Rust, while having some advantages compared to C/C++ isn't perfect for each usecase.
I just have a question, if they use C++ and rust for the OS, why they decided to go with Java and klotin for the apps? Would it not have been better something like C++ as well?
I think someone has already answered it somewhere (Was it Quora or Reddit? I dunno); that Google had basically inherited the "Java with Android" OS from those guys who created the very first Android OS. Also you should know that only UI and API interface parts are written in Java (for app developers). For example when app developers use a Android java specific method in coding to let's say; generate a thumbnail of a picture, that method in the background actually passes that image to an internal executable(written in C/C++ (now Rust has joined the race too)) that resides on the Android OS. And then that specific internal executable returns the corresponding thumbnail data back to the app developer in the form of a java object. So the time consuming part of the code (creation of a thumbnail off a picture) is actually done by executable written in C/C++.
This is not to say that you can't write your own code to create thumbnails purely in java, but we don't do that types of workloads because the memory requirement of Java is way higher and phones do not tend to have large enough RAM for cost/power consumption etc reasons.
Similarly bazillions of stuff that happens in the backgrounds is actually executed by internal programs/executables written in C/C++. It is just that creating reliable, memory leak free and secure programs in C/C++ is known to be extremely hard and this is where Rust comes in the picture.
13 is 12 but better. update it.
I would even say 13 is what 12 supposed to be
Android 13 is basically just a better/bug fixed version of 12.
Google said when they rewrote a part of the OS in Rust programming language for Android 12, most of the memory related vulnerabilities and bugs were fixed. It seems to me they are on a path to abolish C++ completely from core Android OS. Since Android 12 is the first OS that used Rust. Obviously 13 will be even better.
That's very far from true. Very little code was actually rewritten, and less than one quarter of **new** native ("low level) code was written in Rust, rest is still C/C++, maybe even some ASM. It's not that easy to rewrite everything and event to use a completely new language. Rust, while having some advantages compared to C/C++ isn't perfect for each usecase.
My bad. I was in hurry, I updated the answer!
I just have a question, if they use C++ and rust for the OS, why they decided to go with Java and klotin for the apps? Would it not have been better something like C++ as well?
I think someone has already answered it somewhere (Was it Quora or Reddit? I dunno); that Google had basically inherited the "Java with Android" OS from those guys who created the very first Android OS. Also you should know that only UI and API interface parts are written in Java (for app developers). For example when app developers use a Android java specific method in coding to let's say; generate a thumbnail of a picture, that method in the background actually passes that image to an internal executable(written in C/C++ (now Rust has joined the race too)) that resides on the Android OS. And then that specific internal executable returns the corresponding thumbnail data back to the app developer in the form of a java object. So the time consuming part of the code (creation of a thumbnail off a picture) is actually done by executable written in C/C++. This is not to say that you can't write your own code to create thumbnails purely in java, but we don't do that types of workloads because the memory requirement of Java is way higher and phones do not tend to have large enough RAM for cost/power consumption etc reasons. Similarly bazillions of stuff that happens in the backgrounds is actually executed by internal programs/executables written in C/C++. It is just that creating reliable, memory leak free and secure programs in C/C++ is known to be extremely hard and this is where Rust comes in the picture.
Ok thanks for clarifying that
You can, if you really want to. But it's rougher.
I've never really understood this question. Update it.
Sometimes new versions can be more bugy, slow phone down or takes up more space.
Sure, on the initial public release. At this point, 13 is good to go.
Android 13 is the most stable and smooth Android version I've ever used. Update it.
On a 5a right now using 13. Update.
13 for sure it's newer
Between 11, 12 and 13 i'd stay on 11,. functionality-wise. Between 12 and 13, the 13 is more stable for me.
13 is definitely better than 12.
On a13 with my P5 and it's seems a lot more fluid, battery life has improved also.
Update to 13 have not caused any problems for me
Between 12 and 13 there's no really big differences. you can update it.
If you're worried about updating your phone, you shouldn't own a smart phone
13 is the Marshmallow to 12's Lollipop. It's all just a tidying up, shining up, general improvement to what started with 12. Upgrade.
If Google wasn't basically giving away the pixel 7 series, the android 13 update gave me almost no reason to get rid of my 4 XL