[flukus]

I like the polish of manjaro, I just prefer the stability of debian. Polish doesn't mean much when a rolling release breaks your computer.

[shrimp_emoji]

>when a rolling release breaks your computer

Which never happens, even on Arch, where packages aren't held back for 2 weeks like on Manjaro.

Both Arch and Manjaro have been way more stable for me than Ubuntu ever was, and I've used them for like 4 years now. It's counterintuivie, but newer packages seem to work better than older packages. My pet theory for this is that the devs spend most of their attention with the newest versions of their packages. Submit a bug for a DE, and they might tell you to install the newest version to replicate it there (yet you're on Ubuntu...).

I like getting newer packages (which work better) and DEs (which crash less -- see KDE Neon) and faster hardware support.

I'll never go back to a point release distro like Ubuntu or Debian. (Although, apparently, Fedora keeps their packages as new as my Arch system does, the last time I checked, so maybe that'd be an exception. :p)

[flukus]

> Which never happens,

It has happened to me, an update broke my sound card and I didn't know until I tried to use it at a time that was extremely inconvenient to me.

> Submit a bug for a DE, and they might tell you to install the newest version to replicate it there (yet you're on Ubuntu...)

Known bugs have known work arounds, I can deal with that. What I can't deal with is surprise new bugs in cutting edge software.

[OJFord]

> an update broke my sound card and I didn't know until I tried to use it at a time that was extremely inconvenient to me.

That can happen updating infrequently too, and can be harder to work out the cause.

[vinceguidry]

If your kernel gets updated, things that rely on kernel modules may not work properly until the system is rebooted. It's always good to delay kernel updates until you have the time to reboot.