Android
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
🔗Universal Link: [email protected]
💡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]
📰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
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Lemmy App List
Chat and More
view the rest of the comments
interpreted languages are inherently slower than native code. Because huawei controls the hardware they don't need portability and can focus on speed
on a phone, using java will give all the disadvantages with no advantages
look at iphone vs android, for years apple had better battery life and better performance even with half the ram, a worse cpu and smaller batteries
Java isn't an interpreted language any more than C. Java gets compiled into its own machine code developed by Sun. That machine code can be converted to native code or just run "interpreted." (which is more like emulation.)
Maybe you should learn more about something before you criticize it.
I can't think to any program made in java that isn't a memory hog.
Look at the performance of Minecraft java vs native
Or vuze that uses 20x the memory of qbittorrent for doing the same stuff but with less features
So either java devs don't know how to optimize code, or the language itself has some problems
Of course there comes the Minecraft comparison. Which also conveniently ignores the fact that Minecraft can run incredibly fast using certain performance mods. It's not Java, it's just shitty programming / code that hogs its performance.
i did a comparison also with vuze, which is incredibly inefficient compared to other clients
Can you think of any Java programs that aren’t Minecraft, tho?
ok, give me a list of programs made in java that are faster or use less resources than a similar program written in any other decent language when run on the same hardware.
The list has zero entries.
Pretty much large suathes of banking and financing companies, as well as other massive industries, which btw are hiring and pay well.
Java (or rather JVM) is slow at first, but once a JVM has "booted" Java performance wise is on par with the performance of other languages, even system languages. This isn't too apparent in the open source world, because Oracle.
Most infrastructure running on Java have been doing so for decades and continues to be implemented, not because the project managers are idiots, but because the software is portable and java (believe it or not) is getting better, similar to how JS has gotten better post-TypeScript.
So let's not throw the language and infrastructure on the fire in a time when we know *technical debt" is just an executive excuse to allow rushed, faulty and unoptimized programming in order to meet insane deadlines by white collar deadites.
"Agile", "crunch", "technical debt". We've been taken for absolute fools, and now we're blaming the tools. Smh.
Ah sorry - I wasn't dissing Java - I was questioning the commenter's knowledge of Java, given that Minecraft was the example they chose.
The language has nothing to do with what you describe in your last paragraph. There are a lot of reasons what that was happening, and using Java is not one of them. Just the openess of the OS and how it was written was enough to justify such a difference vs a closed OS with a fraction of the possibilities
Also Android is not using just Java, otherwise you would be able to run any normal Java app without "hacks"