You can also install the Iridium Browser fork, which I believe is not far from the original chromium. It integrates nicely to the apt ecosystem (and others too).
I haven't been paying attention to debian packing of chromium, but I am wondering, is the situation on testing or unstable any better?
I used debian on desktops and laptops spanning several decades and IMO a typical desktop user probably doesn't want to stay on stable, that's been my experience anyway. Machines I don't use interactively I've kept on stable though.
I use Debian stable my primary desktop OS and for servers. I just stick to flathub, backports, install from vendor or build from source if needed/easily done. Works well enough for me, although I can see it may not be for everyone.
This makes sense. In recent years I had so many problems compiling things on Debian that needed newer libraries that I caved and went to Ubuntu. But I still run in to library conflicts and I have long felt like I am abusing my system when I try to force some slightly unsupported libraries on to my system to compile someones github code at 3am.
I suppose if I lean more on containers for development and flatpack etc for programs it would be easier to maintain a Debian stable system. Debian has been great for me aside from having older libraries!
Comments
For getting chromium you have a couple of options:
* You can use chromium flatpak version from Flathub
* You can add the Linux Mint repos, and install the chromium package from there (untested)
* You can install the chromium snap (not recommended due to slow launch times)
Sure, but if those are the options then having an old version in the main deb repos is at best unhelpful and confusing.
I use ungoogled-chromium https://github.com/Eloston/ungoogled-chromium
Tho the .deb binary is not up to date yet https://ungoogled-software.github.io/ungoogled-chromium-bina...
You can also install the Iridium Browser fork, which I believe is not far from the original chromium. It integrates nicely to the apt ecosystem (and others too).
https://iridiumbrowser.de/downloads/
I haven't been paying attention to debian packing of chromium, but I am wondering, is the situation on testing or unstable any better?
I used debian on desktops and laptops spanning several decades and IMO a typical desktop user probably doesn't want to stay on stable, that's been my experience anyway. Machines I don't use interactively I've kept on stable though.
I use Debian stable my primary desktop OS and for servers. I just stick to flathub, backports, install from vendor or build from source if needed/easily done. Works well enough for me, although I can see it may not be for everyone.
This makes sense. In recent years I had so many problems compiling things on Debian that needed newer libraries that I caved and went to Ubuntu. But I still run in to library conflicts and I have long felt like I am abusing my system when I try to force some slightly unsupported libraries on to my system to compile someones github code at 3am.
I suppose if I lean more on containers for development and flatpack etc for programs it would be easier to maintain a Debian stable system. Debian has been great for me aside from having older libraries!
You can safely put newer libraries in /usr/local/lib.
https://packages.debian.org/search?searchon=sourcenames&keyw...
buster (misc): 83.0.4103.116-1~deb10u3
bullseye (misc): 83.0.4103.116-3.1
sid (misc): 83.0.4103.116-3.1
experimental (misc): 84.0.4147.105-1
https://tracker.debian.org/pkg/chromium
Why is a snap slower than a flatpak?
Because of its use of a compressed backing store, requiring decompression before launch (IIRC).