this post was submitted on 10 Sep 2023
471 points (97.8% liked)
Asklemmy
43940 readers
754 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I agree with you. But with how fractured the software and hardware space has become. Building native is expensive and time consuming.
For example a web browser is compatible with x86 amd64 armv7 aarch64 on any OS from Windows, Linux, Mac OS, iPad/iOS, and Android.
Which means that if I make 1 web page, I can support all these platforms at once.
The customer doesn't care, they just want funny cat pics.
Building native requires both the hardware (especially if you need to build for the walled garden known as iOS), and frameworks. Where its just easier to recompile chrome, and bake in a Web Page, I.e. react native