5 ms·
Often, great engineering products start out crisp and clean until the product manager, sales and marketing guys, growth managers and evangelists step in and sta
by srvmshr 3y ago
Often, great engineering products start out crisp and clean until the product manager, sales and marketing guys, growth managers and evangelists step in and start adding antipatterns. I am not surprised Ubuntu did it. I am surprised they did it so late. They were slow-cooking this for the last 5 years. And for anyone unwilling to see it: Ubuntu wasn't about building a solid engineering product like RHEL, Debian or Slackware. It was always cashing on making a fork (i.e Debian unstable) more usable. Their core interest is increasing number of installs everywhere, not bringing the next engineering marvel. Flatpak serves that cause beautifully. They only have to worry about sandbox & containers part for software others build.
Ubuntu has tried bold moves - like trying to replace Xorg with Mir. That failed because Mir was raw. But this one might just. Making deb packages second class citizens in a Debian derived OS is so unfortunate.
- synergy20 3y agowe have Debian, which i'm going to use and replace all ubuntu stuff on the server side. on the desktop side, I really just need a browser and a vim editor for 99% of what I do, Debian should be perfectly fine too.
- BaseballPhysics 3y agoAnd honestly, for desktops, Debian testing is plenty stable IME and stays quite up to date. It's what I've run on my laptop for years with absolutely no issues.
- stavros 3y agoHow up to date is it? That might be attractive after years of Ubuntu. How is the proprietary driver support?
- BaseballPhysics 3y agoPretty darn up to date. Tbh I think it's not unusual for it to be more to date than the current Ubuntu stable (which I thought started out as a snapshot of Sid). As for proprietary drivers, the non-free repos have traditionally carried everything I need.
- stavros 3y agoExcellent, thank you.
- subsection1h 3y agoDebian Testing is the least secure Debian distribution: - "Please note that security updates for 'testing' distribution are not yet managed by the security team. Hence, 'testing' does not get security updates in a timely manner."[1] - "Compared to stable and unstable, next-stable testing has the worst security update speed. Don't prefer testing if security is a concern."[2] - "[Testing's] security updates are irregular and unreliable."[3] Most Debian users should use Stable. If a user wants a newer version of some software, they should write a Bash script to install it from source. When I used Debian Stable on the desktop, my installers allowed me to have the latest versions of all of the software of which I wanted the latest versions. If a Debian user wants up-to-date software but they don't want to write their own installers, they should consider using Fedora instead. [1] https://www.debian.org/releases/testing/ https://www.debian.org/releases/testing/ [2] https://wiki.debian.org/DebianTesting https://wiki.debian.org/DebianTesting [3] https://release.debian.org/ https://release.debian.org/
- BaseballPhysics 3y agoYes. I know. For a desktop, bluntly, no, security is not a primary concern (I've also turned off spectre mitigations and so forth), and stable is waaaay too stable for desktop usage. Frankly, this kind of purist ideology--to the point of suggesting people use a different distribution--is simply ridiculous. For servers I'm running on the open internet, yes, you are absolutely right. But in that case I just run stable.
- subsection1h 3y agoSecurity being a primary concern is a "purist ideology"? LOL.
- BaseballPhysics 3y agoThe way you've framed it? Yes. The choices aren't some purist notion of "secure" versus "not secure". Security is a spectrum of practical choices informed by threat models, and it's only one (certainly important!) aspect of the complex choice of selecting an operating system. For example, I would absolutely advise my mother in law to write complex passwords on sticky notes. She's far more likely to fall victim to credential stuffing than to have her apartment broken into and her passwords stolen, and I accept that trying to get her to use a password manager would certainly fail and she'd just fall back on reusing simple passwords. A security purist who thinks in terms of "secure" or "not secure" would scoff that this. Writing down passwords! That cannot be done! But given the threat model and an acceptance of expected user behavior, it's a perfectly valid choice. If I'm running a Linux desktop, I've already made a more secure choice by getting out of the firing line of typical untargeted malware. With some additional basic security hygiene, the greatest threats are a) phishing/social engineering, for which zero days aren't the primary concern, or b) targeted attacks where clearly they are. As I'm not a target of interest, I'm not too terribly worried about the latter. As for the former, distro choice doesn't make much of a difference. So yeah, given that threat model, I'm comfortable waiting the few days it takes for security fixes to trickle down from sid to testing. And if I really cared, I'd follow the guidance mentioned in one of the links you posted, and just pull patches down from sid on an as-needed basis. Switching to a completely different distro, by contrast, would be a ridiculous overreaction give the context and associated trade-offs.
- jdub 3y agoAll of Canonical's most hilarious (and sad) mistakes came directly from the top. But in fairness, so did the initial insight (the gap in the distro market).