When I got my Chromebook in December 2020 or '21, I installed Firefox inside the Linux container (not via flatpak), and run fast.com for lolz, only to realize I got better speeds in it than in the native Chrome. What killed it for me was lack of proper touchscreen support.
Then I learned how to use Linux chroot on the Chromebook (skipping the container layer) and some sort of Wayland proxy and my life was much better.
Then I figured how to almost run Docker natively on it (it 95% worked, but I needed a custom modified runc and some of the isolation features disabled).
The sad thing is that Firefox actually does have proper support for touch screen but you have to manually enable it. The Flags are hidden no away and not available in the settings. I got a laptop/tablet hybrid to run Linux on, and it was definitely a frustrating experience.
Rabbit hole indeed. That wasn't related to my job at the time, lol. The job change came with a company-provided computer and that put an end to the tinkering.
Bought it. Still love the form factor of this thing and I use it (with Fedora) as my private device (mostly running Firefox, some terminal, calculator, etc)
BTW Chrome is also run through the same layer now, to speed up the updates. Albeit is more integrated into the OS, but it's no near the wine you are talking about.
They tried to make a FirefoxOs for mobile in the past. It even shipped with some phone then in true Mozilla fashion (am I being harsh ?) they dumped it and then it became a hit, rebranded as KaiOs in developping countries for unpowerful smartphones
FirefoxOS was a full OS made on web technologies, like Palm/HP/LG's WebOS. That means apps like Contacts or Dialer were JS apps. I believe the other comment about a new FirefoxOS was more about an equivalent to ChromeOS: a simple native UI shell and a browser on laptops.
As a volunteer in an association helping people that have difficulties with new technologies, an OS with just Firefox would really make everything simpler. Just like ChromeOS, you'd only get a browser (more than enough for 95% of non-professional use cases), but without the Google crap (telemetry and the Google account)
I think that's not unlike what ChromeOS is trying to be? With the APIs like WebSerial and WebUSB enabling web apps to do the same things native apps could for years now. (Of course, you can use these in the standalone Chromium, too.)
> an OS with just Firefox would really make everything simpler
It's relatively easy to build a Linux distro that boots straight into Firefox! You can try Cubic, which allows you to create a custom ISO for Debian or Ubuntu with a pretty straightforward GUI wizard. I once used it to create an ISO for an arcade machine.
Firefox OS was too ahead of its time. It made web technologies a first class citizen for mobile app development, well before mobile browsers were as capable as they are today.
Back then, Apple and Android used their million-app inventory to eliminate rival platforms....you needed an app to do anything on a phone back then. Today, nobody's installing new apps if the function can be done on the website.
There's /e/os now. I stand to be corrected but a lot of the privacy issues are more about the ubiquity of 'Google Play Services' rather than Android as a base OS.
Not sure why this gets recommended over LineageOS. It forcefully comes with Micro G, which can't really be removed, unlike Lineage where you can just choose not to install any gapps of any kind and use the device fine.
I think shipping microG by default is a fine choice nowadays. In default setup, it doesn't connect to Google servers at all (/e/ might have different configuration though), but it enables maps and geolocation in apps (using different APIs, not Google). It is also relatively small (4 MB should not be a problem on most devices). That said, I think a no-gapps build would be nice to have, too.
(I use LineageOS as well, though. It works with microG too, but you need to get a build from here instead of the official one: https://lineage.microg.org/)
I gave /e/OS and microG a whirl when I bought my Fairphone (Murena preinstalls it on the phones they sell in the US), and it was cool how much it was able to do without the "real" gApps, but two snags ended up being showstoppers and pushed me to my usual LineageOS+gApps:
1. The Google account for my day job has various security settings that block authentication under various circumstances, including (I guess) Google services running under different signatures/IDs than expected
2. The App Lounge was really crashy for reasons I was never able to discern, and there was little rhyme or reason to certain Play Store apps being missing or uninstallable (namely: my banking app and T-Mobile's voicemail app)
Yeah, I've ran into a fair share of integrity-related problems on microG myself. Notably, apps for most banks I use work fine, but e. g. McDonalds app outright refuses to run. No discounted burgers for me I guess!
The Flame phone was hot garbage. I had one gifted to me at a Mozilla conference. I wanted to offer it to my girlfriend at the time but it was just too terrible for me to do that to her.
Its battery died three weeks later. I still have it if someone in Europe wants it for a museum or some such…
I think it was just-in-time but competing against incredible odds. It was perfectly usable as a first step (I had a cheap ZTE phone [1]) but it came out as the craze for ever more powerful mobiles for taking selfies and sliding down media on social media was reaching feverish levels.
I think of the intervening decade as a lost decade. Imagine if the project did not fold and had iterated this entire time...
I won a dev phone on a competition near my uni (the competition was who will be the fastest to create a simple app for FFOS and I just created a simple html page with a hello world in <p> tags lol), some ZTE one I think. Developed a few games just for myself, it was a fun tech tbh, but the phone was pretty unstable so after a time it just collected dust on my shelf and I sold it to someone.
FirefoxOS sort of lives on through the KaiOS fork, unfortunately many devices come locked which prevents from installing homebrew apps. I have a rooted Nokia 2720 Flip, and while the hardware is abysmal (KaiOS is targeted at emerging markets) you can get quite a bit of functionality out of it (including openstreetmap, podcast/music players, rss readers, google-authenticator-compatible TOTP etc).
I'm reading this on ChromeOS too, but on Chrome. I've tried using Firefox a couple years ago on this machine, but it was the mobile variant from the Android play store which felt a lot like running a mobile app on a large laptop screen, which made everything feel a bit awkward. Maybe it has gotten better since then?
The Play Store version is definitely just running the mobile app version on a large laptop screen. This version is just using the ability to run Linux apps to run the normal desktop version of Firefox directly (albeit in a VM like all the Linux/Android apps on ChromeOS). I'm not sure if hardware acceleration is enabled for the Linux VM for video/graphics things yet though so I'm not sure about how well it performs.
It does. CTRL+T, CTRL+Shift+T, CTRL+L all work. FF mobile doesn't have Dev tools, but Kiwi, a Chromium fork browser, does, so CTRL+Shift+I will bring it up.
My Pixelbook has been collecting dust ever since I switched to my Framework, but back when I was using it I recall Firefox working damn near perfecfly via Crostini. Only quirk was that ChromeOS obviously expects a different browser, so getting other software to reliably open links in Firefox instead of the built-in Chrome was less than foolproof, but it otherwise worked exactly as well as on an ordinary (GNU/)Linux desktop system.
I ran Firefox in Crostini once. I'd say it was an "eh" experince. But then I installed Linux on it. Too bad that the way I installed Linux on it is being discontinued...
I just ran the FF Android app on ChromeOS when I had one. I've installed other apps like Obsidian through the Linux container, but it's annoying to use as launching the app kicks off a Linux container load sequence which is pretty lengthy.
It's actually easier than what the document shows you: Once you get to the Debian shell do apt-get install firefox-esr instead of installing the flatpack. I assume they don't tell you that, because then you end up with the Debian build of Firefox instead of the Mozilla's
I am said maintainer. Note that's not part of my work at Mozilla, and that doesn't make the Debian package endorsed by Mozilla as the way to get Firefox on Debian.
I’m curious if there is a user segment truly interested in this feature/product and what their use case is. Naively this feels like a situation of “why on earth would you do this?”
For what it's worth, I think I am. I got a gift voucher from work a little while back, combined it with a few other gift vouchers I had lying around and bought a convertible ChromeOS tablet. It seemed like a good choice, since I didn't have a tablet form-factor device at the time, it was a lightweight ARM thing that could natively run Android apps and Linux apps, and it ran a mostly-OSS stack including open source graphics drivers. I found it way more appealing than the equivalent devices running Android or Windows.
As soon as I got it home, I realized that all my passwords and bookmarks were in my Firefox account, and I remembered that I don't really like the idea of using Chromium-based browsers on the web for philosophical reasons. I tried to install Firefox, but the Linux version didn't work too well in tablet mode, so I had to suck it up and use Chrome. Kind of dumb on my part, I know, but I still like the device, and I'd like it even more if Firefox worked better on it.
I can see it being useful in a corporate setting to limit which sites you can visit with Chrome to just your secure admin panels and internal apps. Then use Firefox to go to dangerous places like… the Internet.
That way if one of your users clicks a link in a phishing email Chrome simply won’t open it.
I have a quest to ween from the chrome browser but owning a chromebook makes it hard. I have a samsung chromebook plus and firefox detects it as a phone so the interface layout is wrong. I hear good reviews for the steam deck. Steam should go ahead and bring the Steam Book with Firefox support. I would take a look at that. I won't mind that the only think I could play is sudoku but it has to be touch screen with a stylus.
I have a cheap Lenovo Chromebook Flex 3 with a MediaTek MT8183 processor that I picked up for under $79 at a BestBuy Black Friday sale. I run Firefox ESR on it with no problems in the Linux container, no flatpak needed. Here's all you need:
I have a Lenovo Chromebook Duet (the first gen one) which I think runs the same processor. Though the 4GB RAM is a little bit limiting so I don't use it that often.
I'm a huge Firefox fan (both on PC and Android) and I think Firefox for Android on ChromeOS is terrible, practically unusable. I know my Chromebook is cheap but Firefox runs ultra slow. It also randomly flickers to a black screen and crashes occasionally.
I don't know if it's just me or this is just how it runs.
It's already weird and clunky on a phone. I do it nonetheless, but I'm experiencing weirdness with pwa's, and of course many apps (sometimes the OS itself) defaults to Chrome for breaking out to web-pages.
Maintenance-free, auto-updating, single-purpose computer? For many people, it's everything they need a computer to do, with more convenience and less fiddling around with stuff they don't understand.
I like the form factor. Small but not too small, ok keyboard, good hardware: i7, 16GB RAM, 512GB SSD, converts to tablet. I run Fedora Linux after removing ChromeOS (the only thing I'm missing is running Android apps). Bought used for cheap (they were never officially distributed in Poland to my knowledge). Taking about Google Pixelbook "eve"
I can understand the appeal. I have a 2018 MacBook air for that exact reason. Although it's slightly more useful becase having a proper terminal that can run Docker and stuff has saved my ass more than once.
I'd be down to replace it with a Chromebook if the model looks and feels as good as the air.
Chromebooks are not for everyone, but they have some real advantages. Generally less expensive, highly secure and easy to use. Seamlessly run Android apps and Linux apps. Great integration with your Android phone. Os stays clean over time.
I personally run fedora and do a lot of development, but if I was limited to a Chromebook I could do what I needed and not hate it.
Eh... I would never purchase one myself but they have some good use cases. They're great for schools because kids always break devices and they're cheap to get replacement parts for. They're also quite easy to use for web browsing, which is basically all most people do these days. Another great use is for old people. Handing a Windows device to a senior is almost a guaranteed virus/malware host.
Hardware-wise, my Pixelbook was fantastic. 3:2 screen, touch+pen, solid yet lightweight, decent enough performance.
The software was... tolerable, at best, but the support for Linux desktop and Android apps made it much more tolerable than Windows or macOS. That ChromeOS technically represents the fabled "Year of the Linux Desktop" is a depressing thought, but for what it is, it ain't terrible.
Then I learned how to use Linux chroot on the Chromebook (skipping the container layer) and some sort of Wayland proxy and my life was much better.
Then I figured how to almost run Docker natively on it (it 95% worked, but I needed a custom modified runc and some of the isolation features disabled).
Then I changed jobs. Was fun though