That said, Debian Stable is an ideal desktop OS for older hardware. I have a Mac Mini from the first generation of Intel Macs, upgraded to a Core 2 Duo CPU, that runs BunsenLabs Linux (based on Jessie and a 3.x kernel) just fine. In fact, it's one of the few Linux distros that still supports that 11 year old machine, long after even Apple left it behind.
Why Use Debian Stable on the Desktop?
11–20 of 61 posts
Re: Why Use Debian Stable on the Desktop?
#12Using Debian Stable on a desktop is probably the closer to hell that you could ever get. Imagine to never be able to get that one feature you need because it's only in a more recent version. The best option for a stable desktop is Gentoo, where you can run old software but then unmask recent stuff if you need it. As a recent example I'll say that MTP support in stable (libmtp) was flaky for my mobile phone. With Debi…
Re: Why Use Debian Stable on the Desktop?
#13As a Debian user for 15 years, I like it, but as a developer looking to contribute packages, I am displeased. I can't figure out how to update Gambit Scheme to the newest version by making a package, setting up a local repo, etc. The documentation on the subject in debian is all over the place on many sites giving conflicting answers. Gentoo and Arch in my limited experience are much simpler to build packages for. Re…
Re: Why Use Debian Stable on the Desktop?
#14For those who are to afraid to run Arch, consider openSUSE Tumbleweed. It is as up to date (or more so) as Arch Linux but they do a lot of automated testing, plus they do a lot of automatic snapshots so you can go back if needed (that is if you are willing to run Btrfs).
Re: Why Use Debian Stable on the Desktop?
#15Or in other words, "I use Debian Stable on my home computer and here's how I've justified it to myself". If Debian Stable does everything you want out of an operating system, by all means use it, there's no reason not to, but some other people may want to make use of the newer features of Linux and its surrounding ecosystem that aren't available in Debian Stable yet. The idea that Debian Stable is a good choice for a…
The more i have had to deal with the Linux ecosystem, the less i want to do with the bleeding edge of it. Because you will find shit breaking, willfully, every other month or so, because some caffeine addled code monkey thought he could do a decade+ usage-tested lib better in a new language over the weekend.
Re: Why Use Debian Stable on the Desktop?
#16Site is down. Google Cache: https://webcache.googleusercontent.com/search?q=cache:nHJYRo... I'll never understand why serving static(!) sites is so hard. Are modern blog systems still that bad? HN traffic is far below 100 req/sec (perhaps below 10 req/sec), which should be an absolute no-brainer for any modern webserver. [1] Heck, given a good internet connection, one should be able to run 10 such blogs on a Raspberr…
challenges start at 100000 req/sec
Only if you have a well configured cache in front of your cms. If you don't expect any significant traffic, it's perfectly reasonable to serve directly from your cms. And that might be super slow because optimizing a cms for perfomance does not make sense. That should be the job of a cache in front of the cms.Re: Why Use Debian Stable on the Desktop?
#17Site is down. Google Cache: https://webcache.googleusercontent.com/search?q=cache:nHJYRo... I'll never understand why serving static(!) sites is so hard. Are modern blog systems still that bad? HN traffic is far below 100 req/sec (perhaps below 10 req/sec), which should be an absolute no-brainer for any modern webserver. [1] Heck, given a good internet connection, one should be able to run 10 such blogs on a Raspberr…
It's not hard. They're all adding stupid bloat for no good reason.
When my blog was on the frontpage, traffic peaked at 1 Mbit/s (that's megabits, not megabytes) and CPU load peaked at 5% of a single core (and only because that box runs a dozen services in parallel).
Everyone who's blog cannot withstand the HN crowd deserves to have their computer operator's license revoked.
Re: Why Use Debian Stable on the Desktop?
#18Site is down. Google Cache: https://webcache.googleusercontent.com/search?q=cache:nHJYRo... I'll never understand why serving static(!) sites is so hard. Are modern blog systems still that bad? HN traffic is far below 100 req/sec (perhaps below 10 req/sec), which should be an absolute no-brainer for any modern webserver. [1] Heck, given a good internet connection, one should be able to run 10 such blogs on a Raspberr…
challenges start at 100000 req/sec Only if you have a well configured cache in front of your cms. If you don't expect any significant traffic, it's perfectly reasonable to serve directly from your cms. And that might be super slow because optimizing a cms for perfomance does not make sense. That should be the job of a cache in front of the cms.
Static site generators are a thing now.
Re: Why Use Debian Stable on the Desktop?
#19Damn. Maybe I need to look around.
Re: Why Use Debian Stable on the Desktop?
#20As a Debian user for 15 years, I like it, but as a developer looking to contribute packages, I am displeased. I can't figure out how to update Gambit Scheme to the newest version by making a package, setting up a local repo, etc. The documentation on the subject in debian is all over the place on many sites giving conflicting answers. Gentoo and Arch in my limited experience are much simpler to build packages for. Re…
I regularly build Arch packages. I once tried to build a Debian package, followed the tutorial, but gave up after nearly two hours. The amount of ceremony involved in Debian packaging is just absurd.
I'm guilty of this myself. The script I made is heavily inspired by Arch. The resulting script for Firefox is like this: https://github.com/qznc/simpledeb/blob/master/test/firefox.D...