WebOS powers TVs now and, from the article, Amazon intends this replacement to cover their Fire tablet line. WebOS ticks all their boxes, especially since apps in Amazon’s new flavor are intended to be delivered as React Native web apps.
So despite the desire for one, Vega won’t be an Android-killer, won’t bring an influx of big name apps to benefit regular Linux distros, nor see Amazon do something crazy cool like create its own Linux tablet UI.
You know how much overhead Electron apps are? Well, here’s React Native! Enjoy all the annoyances of mobile development with the ugliest that is React!
It actually works pretty great, it genuinely does compile to native code pretty well. The js code just drives - everything visual or I/O is native, so it’s faster than you’d think
Idk if I’m the only person who thinks this, but I feel like React has gotten worse over the last couple of major versions. Not only does the code look a lot messier when you use their new syntax, but the end result seems unreliable. Facebook is barely even usable now. Their history management is laughable, and it’ll drop you out of the site randomly when using the back buttons. I used to think React was really neat, but I’m not a big fan anymore. There’s too much re-engineering for problems that were solved decades ago.
If you like it, then use it. There’s no point in jumping every time some new framework comes out. Most of them don’t last. I have used React off and on since it came out, and I personally don’t like how the syntax has changed. My personal website is React and doesn’t have any browser history issues. Idk what’s up with Facebook history management. I guess they just don’t care very much because they’re too busy trying to gobble up data.
React is having the same problems Angular had, and jQuery had. New ECMAscript features make formerly complex things easier, and JS frameworks adapt.
Lots of solutions. But as more edge cases start to show up, they continue to add more and more little things that shape the language into more different variants.
Many of the changes are pretty good. But New devs will go, “Why are there 7 ways to do this React thing?” And that adds to the noise.
Again, that’s not a React problem. It’s just coding in general. PHP also had a “damn you ugly” phase. But unlike PHP, I don’t think React (and most JS frameworks of today) will continue to be as popular as some hot new JS framework in 2027-2030 sweeps the landscape.
And PHP will still be chugging along. lol. It’s weird that React syntax went from being fairly pretty, and structured, to looking like a plate of spaghetti. Usually languages and frameworks go the other direction.
I love how PHP 7 looks, and PHP 8 only continues to improve.
Totally agree. React is going backwards. Vue is so attractive. Heck, I’m even starting to rebuild react apps in Web components because react is getting weird.
Installing Microsoft TTF packages on my distro used to be one of the first things I did. Sometime back I ended up finding suitable replacements that are stock (less packages, less installation steps, less proprietary software.)
I’ve recently found the Inter-font package (mentioned in one of Infinitely Galactic’s YouTube videos. It’s excellent, clean like Noto Sans, but slightly more readable. I’ll swap in the Ubuntu font every now and then for fun though, I really like that one too.
Yes, but those minor traces are easy enough to remove, especially if you don't care about being "ceritified" by Google (i.e. are not planning to run the Google services).
If my device is compatible, does it automatically have access to Google Play and branding?
No. Access isn’t automatic. Google Play is a service operated by Google. Achieving compatibility is a prerequisite for obtaining access to the Google Play software and branding. After a device is qualified as an Android-compatible device, the device manufacturer should complete the contact form included in licensing Google Mobile Services to seek access to Google Play. We’ll be in contact if we can help you.
Google services are entirely missing from Android open source. The Google Play package is what contains the entirety of Google’s services.
Not sure if anyone remembers but back when cyanogenMod was the go-to, early versions had Google services included. Google sent a cease and desist notice and said it was a license violation. You cannot distribute it as part of the OS by default. The next release of cyanogenMod had it removed. Users had to flash the package if they wanted it.
Right but the topic was about google’s data harvesting and what I meant was that you can’t just grab any AOSP distribution if you want to minimize that, you need to pick one that replaces the parts that send data to google. LineageOS for example still phones google for quite a number of services.
As far as “easy to remove” goes, I think that’s kind of debatable if you want to do it in a way that’s sustainable long term considering the effort that goes into e.g. GrapheneOS or DivestOS.
Edit: here is a list of the kind of stuff you need to watch out for if you want to minimize the data sent to google
I was answering under the assumption/the context of of "Amazon wants to release an Android-based OS that doesn't contact any of Googles services".
So, when I said "easy enough to remove" that was relative to releasing any commercial OS based on AOSP, as in: this will be one of the smallest tasks involved in this whole venture.
They will need an (at least semi-automated) way to keep up with changes from upstream and still apply their own code-changes on top of that anyway and once that is set up, a small set of 10-ish 3-line patches is not a lot of effort. For an individual getting started and trying to keep that all up to do date individually it's a bit more of an effort, granted.
The list you linked is very interesting, but I suspect that much of that isn't in AOSP, my suspicion is that at most the things up to and excluding the Updater even exist in AOSP.
Nice! And they will probably differentiate from the competition by allowing GPL applications and sideloading, and having a total control for your privacy and no tracking, right?
hopefully they’ll design some package manager incompatible with android at the most basic level - and then double down when it’s proven to be a huge mistake. a good tick upwards for dev jobs, but the time for actual competition was over 10 years ago. this will fail miserably.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.