Android

17648 readers

141 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.

Support, technical, or app related questions belong in: [email protected]

For fresh communities, lemmy apps, and instance updates: [email protected]

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below

Rules

Stay on topic: All posts should be related to the Android OS or ecosystem.
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

See thread

Chat and More

founded 1 year ago

MODERATORS

[email protected]

Ram in phones? (lemmy.ml)

submitted 9 months ago by [email protected] to c/[email protected]

47 comments fedilink hide all child comments

I don’t get why Android phones have so much ram.

They often have more ram than my wife’s MacBook and the same or my as my desktop.

How much ram is needed if you’re not gaming or video editing?

In my case, it’s a very occasional picture or video recorded and then just social media apps and web. Do I need to get a phone with 12gb? Or is that just thrown in there for marketing?

you are viewing a single comment's thread
view the rest of the comments

[–] ICastFist 2 points 9 months ago (1 children)

Software today is much more capable than it was 12 years ago.

Depends on the area. For most of the corporate world, nothing changed. Databases mostly work the same since the 80s, the only new thing since then are data warehouses and nosql variants, due to the sheer volume of data available nowadays. Office applications (Word, Excel and similars) are pretty much the exact same thing as 25 years ago. CAD and 3D modelling tools haven't changed much in the meantime, but hardware got much beefier, making part of the process faster.

So why shouldn’t the phone have similar memory requirements to a PC?

For the same reason you didn't need 8gb of RAM just to open fucking Chrome back in 2010. Changing tabs was as instant back then on a shit computer as changing apps is nowadays on any phone, with significantly less resources needed for that. Loads of apps are little more than glorified "single page browsers", they just load a special version of the site with a couple extra bells and whistles. You can very easily run Spotify, Youtube, TikTok, Discord, Gmail, Xitter and more on a single browser and change tabs instantly with a single click. The mobile browser experience with them is bad because why make it good when "the app is better"?

let me also remind you of the fact that the mobile gaming market is the largest of them all by far.

And most games aim at the lowest common denominator (both regarding phone specs and "type of game") because they want to reach the widest audience possible. A lot of people use Unity to make simple 2D games, yet that thing is bloated as all hell. Does it facilitate development? Absolutely. That doesn't excuse it for being a mess.

As a side note, did you know that the PS2 had 32MB of RAM and its main CPU was a custom RISC running at 300MHz? You know, the console that let people play God of War 1 and 2, GTA San Andreas. "Oh, but its sole purpose was for gaming and it had a specific graphics core" - true, but once your application is front and center in a phone, it can hog 90% of the CPU and eat any free RAM, which, if your phone has 2GB total, and ~1.5GB is used by other apps and the system, you still have some 400MB to play with. The OS can get in the way and does add overhead, which ends up mostly being extra CPU time.

And honestly, I don’t remember Android phones from over a decade ago ever actually feeling fast. They might have been all right for a while but, in my experience, old phones would usually turn into a slog quickly.

A Galaxy S2, back on release, was really fast compared to its peers. Once its specs became mid-low end, it started to feel significantly slower, that's true. Could've been the bloat catching up.

[–] [email protected] 0 points 9 months ago

Depends on the area. For most of the corporate world, nothing changed.

Well, we are talking about consumer technology here.

For the same reason you didn't need 8gb of RAM just to open fucking Chrome back in 2010. Changing tabs was as instant back then on a shit computer as changing apps is nowadays on any phone, with significantly less resources needed for that.

There isn't quite another platform that has changed as dramatically as the web over the last few years. Just look at all those new APIs. Especially with the introduction of WebAssembly, we have reached a point where running actual software in the browser has become a viable option. Back in 2010, most websites consisted mainly of static content and maybe a bit of Flash and JavaScript here and there.

Loads of apps are little more than glorified "single page browsers", they just load a special version of the site with a couple extra bells and whistles. You can very easily run Spotify, Youtube, TikTok, Discord, Gmail, Xitter and more on a single browser and change tabs instantly with a single click.

Do so and check your memory usage.

And most games aim at the lowest common denominator (both regarding phone specs and "type of game") because they want to reach the widest audience possible. A lot of people use Unity to make simple 2D games, yet that thing is bloated as all hell. Does it facilitate development? Absolutely. That doesn't excuse it for being a mess.

Having a look at the list of most popular mobile games, you will see that recent ones usually aren't simple 2D games.

As a side note, did you know that the PS2 had 32MB of RAM and its main CPU was a custom RISC running at 300MHz? You know, the console that let people play God of War 1 and 2, GTA San Andreas. "Oh, but its sole purpose was for gaming and it had a specific graphics core" - true, but once your application is front and center in a phone, it can hog 90% of the CPU and eat any free RAM, which, if your phone has 2GB total, and ~1.5GB is used by other apps and the system, you still have some 400MB to play with. The OS can get in the way and does add overhead, which ends up mostly being extra CPU time.

That's really not comparable at all. Games back then were specifically optimized for a single console with a single hardware configuration. Android apps today target millions of different devices and mostly aren't even native. That's just how it works and it isn't really an issue since RAM has become dirt cheap. There isn't really any downside to just having a lot of RAM when it only increases the price by a few dollars.

A Galaxy S2, back on release, was really fast compared to its peers. Once its specs became mid-low end, it started to feel significantly slower, that's true. Could've been the bloat catching up.

Compared to it's peers? Maybe. But it definitely couldn't keep dozens of apps running in the background and allow immediate switching between them without reloads. Even with the lower requirements of apps back then.