Debian doesn’t break often because they don’t change things just for the sake of changing them. Nice and stable. Even if you do break something, a guide published 5 years ago describing how to solve the problem would probably still mostly work today.
I used Debian testing on my production servers for a long time. They say not to use it in production, but even as a “testing” release it’s still more stable than some other distros.
I use Debian stable on all my servers now, though (except for my home server which runs Unraid). I don’t have time to keep a rolling build up-to-date like I used to.
It’s from the phrase “big wheel”, meaning a person with a lot of power/influence. Similar to “big cheese”… It would have been better to use “cheese” instead of “wheel” IMO.
It’s usually the apps themselves doing weird things - Using undocumented APIs, expecting the system to be set up in a particular way, relying on bugs in the OS, etc. Windows tries, and actually emulates old bugs for popular apps so they continue to work, but it can’t be bug-compatible forever.
Apps/games that work on XP should mostly work on newer versions as long as you set them to run with Windows XP compatibility (in the settings of the EXE), but there’s definitely edge cases.
Plenty of old apps still run fine. I’ve got VB6 apps I wrote in the mid 2000s that still run. A previous employer has DLLs from 1999 still running in production on Windows Server - VB6 COM components with hundreds of thousands of lines of code in total. I’m reasonably sure than Office 2000 still works, too.
You do sometimes have to change the compatibility settings and run the apps as administrator (since they were designed for Windows 9x which didn’t have separate admin permissions) but often they work.
Even some 16-bit apps work fine as long as you use a 32-bit version of Windows (Windows 10 or older; 11 dropped the 32-bit build). The 64-bit versions of Windows don’t have the NTVDM component that’s required to run 16-bit Windows and DOS apps. It’s an optional component on 32-bit Windows and you need to manually install it.
A lot of effort is put in to backwards compatibility in Windows - Raymond Chen has blogs and books about it.
I ran my college laptop through 15 system upgrades without any issues, nothing has been that reliable for me.
I’ve got a VPS running Debian Bookworm (12.0, latest version at the moment) that I haven’t reformatted since Etch (4.0, 2007). I’ve just done an in-place upgrade every time a new version is out.
That’s not a GUI setup though, so probably more stable when updating…
I’ve been using Debian on servers for maybe 20 years now, so I’m very experienced with Debian on servers, but I’ve never really used the Fedora/RedHat/CentOS side of things.
The last time I used a Linux desktop was Ubuntu back in 2006 or so, back when it was still a new up-and-coming distro and they’d send you a free CD (very useful since I was using dialup at the time).
I’m thinking about which distros I should try since I want to switch from Windows. I’ve heard Mint and Pop OS are good? I might try Debian too. I used to love tweaking the OS back in my teenage years, but now I’m in my 30s and don’t have time to fix random breakages… I just want something stable that works well. (that’s why I was considering Debian)
I’m pretty familiar with Linux server management, but haven’t ran Linux on the desktop in a very long time (I still remember the days of XFree86, which was the predecessor to X.org). If I install a mainstream desktop distro today (Ubuntu, Mint, whatever is popular now), does it come with X11 or Wayland out-of-the-box?
This reminds me of something I saw online maybe 20 years ago now. Someone created a torrent with a name like “every IP address ever (hacking tool)” and uploaded it to Suprnova, which ended up having thousands of people seeding it. It was just a text file with every IPv4 from 0.0.0.0 to 255.255.255.255 😂
No. All the official packages in the main repo get security updates from the Debian security team.
Only the packages in contrib, non-free and non-free-firmware don’t have official security updates and rely on the package maintainers. These are not considered part of the Debian distro, and I don’t even have them enabled on my servers.
Out-of-the-box, Debian only enables the main repo, plus the non-free-firmware one if any of your devices require it (e.g. Nvidia graphics, Realtek Bluetooth, etc). You have to manually enable contrib and non-free, and by doing that, it’s assumed you know what you’re doing.
In the case of non-free and non-free-firmware, they can be closed source software (like the Nvidia drivers) or have a non-open-source license that doesn’t allow distributing modified versions. In those cases, the Debian team is unable to patch them even if they wanted to.