LinuxPhoneApps
alpha.linuxphoneapps.org
LinuxPhoneApps
1–10 of 31 posts
Re: LinuxPhoneApps
#2Linux phone apps: "Let's reimplement all of Android's basic app system in a less secure language because Java isn't cool and Unix should be always in C"
Re: LinuxPhoneApps
#3Linux phone apps: "Let's reimplement all of Android's basic app system in a less secure language because Java isn't cool and Unix should be always in C"
That's okay, nobody will ever use these applications, so they don't pose a security issue to anybody.
Re: LinuxPhoneApps
#4Linux phone apps: "Let's reimplement all of Android's basic app system in a less secure language because Java isn't cool and Unix should be always in C"
Linux phones are much more about freedom, privacy, control, ownership and choice than about java not being cool. I watch the linux phones progress since qt greenphone and your comment is the worst one I've read about it more than a decade.
Re: LinuxPhoneApps
#5Glad to see us moving more and more to a linux phone ecosystem. Obviously this ecosystem is still early but exciting to see the foundations being laid.
Re: LinuxPhoneApps
#6Linux phone apps: "Let's reimplement all of Android's basic app system in a less secure language because Java isn't cool and Unix should be always in C"
Linux phones are much more about freedom, privacy, control, ownership and choice than about java not being cool. I watch the linux phones progress since qt greenphone and your comment is the worst one I've read about it more than a decade.
My comment wasn't about the Linux phone (I get what you wrote) but about Linux phone apps. The smarter play would have been to fork AOSP, but if not that, at least do not write the userland in C.
Re: LinuxPhoneApps
#7Earlier quoted context omitted.
Linux phones are much more about freedom, privacy, control, ownership and choice than about java not being cool. I watch the linux phones progress since qt greenphone and your comment is the worst one I've read about it more than a decade.
My comment wasn't about the Linux phone (I get what you wrote) but about Linux phone apps . The smarter play would have been to fork AOSP, but if not that, at least do not write the userland in C.
Using AOSP really looks like a smart move. F-droid is already a finely curated app repository and very clear about anti-features.
Nevertheless, I don't think linux on phones, apart from the UI, is very different from linux on the desktop. So it can be stable and secure. If anbox manages to run well on these distros then there will be no lack of apps.
The UI will take some time to mature but, after all, not using AOSP doesn't seems like a dumb move.
Re: LinuxPhoneApps
#8Linux phone apps: "Let's reimplement all of Android's basic app system in a less secure language because Java isn't cool and Unix should be always in C"
Linux phones are much more about freedom, privacy, control, ownership and choice than about java not being cool. I watch the linux phones progress since qt greenphone and your comment is the worst one I've read about it more than a decade.
I don't see how AOSP is not free enough, or is not Linux enough underneath.
I think these programs are much less resource-hungry than a JVM-based phone suite.
Though yes, I wish it wasn't C or C++, but Rust, Zig, Golang, D, what have you. The problem is that all GUI toolkits worth considering in the native space are either deeply C (GTK, fltk), or deeply C++ (Qt), and adapting them to these languages is neither idiomatic nor safe.
Re: LinuxPhoneApps
#9Earlier quoted context omitted.
Linux phones are much more about freedom, privacy, control, ownership and choice than about java not being cool. I watch the linux phones progress since qt greenphone and your comment is the worst one I've read about it more than a decade.
I don't see how AOSP is not free enough, or is not Linux enough underneath. I think these programs are much less resource-hungry than a JVM-based phone suite. Though yes, I wish it wasn't C or C++, but Rust, Zig, Golang, D, what have you. The problem is that all GUI toolkits worth considering in the native space are either deeply C (GTK, fltk), or deeply C++ (Qt), and adapting them to these languages is neither idiom…
Note that Android has been using ahead of time compiling, not JVM, for a better part of a decade now. Java does not imply JVM run-time.
Re: LinuxPhoneApps
#10Linux phone apps: "Let's reimplement all of Android's basic app system in a less secure language because Java isn't cool and Unix should be always in C"
We don't need to reinvent anything, just adapt desktop programs to a smaller screen. You can still run java programs if you prefer using a slow, overcomplicated programming language. However I will stick to GTK4.