this post was submitted on 02 May 2024
735 points (96.8% liked)
linuxmemes
21255 readers
17 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
Being able to practially develop anything without running Google's proprietary build of Android SDK can be enough for devs to see the difference.
It might be very similar on the surface, for casual person installing app from appstore. But the whole ecosystem above the Linux kernel and below app interface is barely comparable. No Flatpak, Wayland, SystemD, glibc, PipeWire, etc.
The way apps are build, most of the times does not matter what kernel is at the bottom. What matters are toolings and the ecosystem.
Android could be build on Windows NT and most won't notice (remember Windows Phone? Not looking at UI/UX design, it felt really similar), yet we wouldn't call Android as being the same as Windows.