[ithrow]

How do you handle chromium in Debian stable? It always lags behind significantly behind chromium/chrome releases.

[capableweb]

The trick: Don't use Debian Stable, use Testing. Despite it's name compared to "stable", Testing is pretty stable in my experience.

- Chrome Stable - 112.0.5615.137

- Debian Bullseye (stable) - 108.0.5359.94

- Debian Bookworm (testing) - 112.0.5615.49

Most people I know who run Debian for personal desktops uses Testing, not Stable. Vice-versa for servers.

[doubled112]

The security repo that is added by default has newer Chromium packages

https://wiki.debian.org/Chromium

https://security-tracker.debian.org/tracker/source-package/c...

- buster 90.0.4430.212-1~deb10u1

- bullseye 108.0.5359.94-1~deb11u1

- bullseye (security) 112.0.5615.121-1~deb11u1

- bookworm 112.0.5615.49-2

- sid 112.0.5615.138-1

[skovati]

My philosophy has been to let the distro package manager handle system packages (kernel, OpenSSL, etc) but then use flatpak [1] to install user progs like Chromium and VSCode so I get bleeding edge releases and sandboxing.

[1] https://flathub.org/apps/details/org.chromium.Chromium

[wmf]

And by bleeding edge you mean stable.

[forty]

I use Firefox ESR with Debian stable + backports, and the internet seems to work as far as I can tell (I'm not doing anything fancy with it though)

[pmontra]

I use Firefox and I switch to Google Chrome for the very few cases when it's too difficult to make a web site work with Firefox plus all the privacy addons I added to it, maybe not every month.

I think I downloaded the installer from Google and I got this

  deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main

in /etc/apt/sources.list.d/google-chrome.list now.