{"id":7046,"date":"2019-01-01T05:25:48","date_gmt":"2019-01-01T05:25:48","guid":{"rendered":"https:\/\/www.appservgrid.com\/paw92\/?p=7046"},"modified":"2019-01-08T10:13:56","modified_gmt":"2019-01-08T10:13:56","slug":"the-state-of-desktop-linux-2019","status":"publish","type":"post","link":"https:\/\/www.appservgrid.com\/paw92\/index.php\/2019\/01\/01\/the-state-of-desktop-linux-2019\/","title":{"rendered":"The State of Desktop Linux 2019"},"content":{"rendered":"<p><em>A snapshot of the current state of Desktop Linux at the start of<br \/>\n2019\u2014with comparison charts and a roundtable Q&amp;A with the leaders of three top<br \/>\nLinux distributions.<\/em><\/p>\n<p>I&#8217;ve never been able to stay in one place for long\u2014at least in terms of which Linux distribution I call home.<br \/>\nIn my time as a self-identified &#8220;Linux Person&#8221;, I&#8217;ve bounced around between a<br \/>\nnumber of truly excellent ones. In my early days, I picked up boxed copies of<br \/>\nS.u.S.E. (back before they made the U uppercase and dropped the dots<br \/>\nentirely) and Red Hat Linux (before Fedora was a thing) from store shelves at<br \/>\nvarious software outlets.<\/p>\n<p>Side note: remember when we used to buy Operating Systems\u2014and even most<br \/>\nsoftware\u2014in actual boxes, with actual physical media and actual printed<br \/>\nmanuals? I still have big printed manuals for a few early Linux versions, which, back then, were necessary for getting just about everything working<br \/>\n(from X11 to networking and sound). Heck, sometimes simply getting<br \/>\na successful boot required a few trips through those heavy manuals. Ah, those<br \/>\nwere the days.<\/p>\n<p>Debian, Ubuntu, Fedora, openSUSE\u2014I spent a good amount of time living in<br \/>\nthe biggest distributions around (and many others). All of them were<br \/>\nfantastic. Truly stellar. Yet, each had their own quirks and peculiarities.<\/p>\n<p>As I bounced from distro to distro, I developed a strong attachment to just<br \/>\nabout all of them, learning, as I went, to appreciate each for what it<br \/>\nwas. Just the same, when asked which distribution I recommend to others,<br \/>\nmy brain begins to melt down. Offering any single recommendation feels<br \/>\nsimply inadequate.<\/p>\n<p>Choosing which one to call home, even if simply on a secondary PC, is a<br \/>\ndeeply personal choice.<\/p>\n<p>Maybe you have an aging desktop computer with limited RAM and an older, but<br \/>\nstill absolutely functional, CPU. You&#8217;re going to need something light on<br \/>\nsystem resources that runs on 32-bit processors.<\/p>\n<p>Or, perhaps you work with a wide variety of hardware architectures and need a<br \/>\nsingle operating system that works well on all of them\u2014and standardizing<br \/>\non a single Linux distribution would make it easier for you to administer<br \/>\nand update all of them. But what options even are available?<\/p>\n<p>To help make this process a bit easier, I&#8217;ve put together a handy set of<br \/>\ncharts and graphs to let you quickly glance and find the one that fits your<br \/>\nneeds (Figures 1 and 2).<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.linuxjournal.com\/sites\/default\/files\/styles\/max_1300x1300\/public\/u%5Buid%5D\/LJ-Jan-2018-BigChart-1.png\" alt=\"&quot;&quot;\" width=\"1004\" height=\"1300\" \/><\/p>\n<p><em>Figure 1. Distribution Comparison Chart I<\/em><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.linuxjournal.com\/sites\/default\/files\/styles\/max_1300x1300\/public\/u%5Buid%5D\/LJ-Jan-2018-BigChart-2.png\" alt=\"&quot;&quot;\" width=\"1004\" height=\"1300\" \/><\/p>\n<p><em>Figure 2. Distribution Comparison Chart II<\/em><\/p>\n<p>But, let&#8217;s be honest, knowing that a particular system meets your hardware<br \/>\nneeds (and preferences) simply is not enough. What is the community like?<br \/>\nWhat&#8217;s in store for the future of this new system you are investing in? Do<br \/>\nthe ideals of its leadership match up with your own?<\/p>\n<p>In the interests of helping to answer those questions, I sat down with the<br \/>\nleaders of three of the most prominent Linux distros of the day:<\/p>\n<ul>\n<li>Chris Lamb: Debian Project Leader<\/li>\n<li>Daniel Fore: elementary Founder<\/li>\n<li>Matthew Miller: Fedora Project Leader<\/li>\n<\/ul>\n<p>Each of these systems is unique, respected and brings<br \/>\nsomething truly valuable to the world.<\/p>\n<p>I asked all three leaders the exact same questions\u2014and gave each the chance to<br \/>\nrespond to each other. The topics are all over the place and designed to<br \/>\nhelp show the similarities and differences between the distributions, both in terms of<br \/>\ngoals and culture.<\/p>\n<p>Note that the Fedora project leader, Matthew Miller, was having an unusually<br \/>\nbusy time (both for work and personally), but he still made time to answer as<br \/>\nmany questions as he could. That, right there, is what I call dedication.<\/p>\n<p>Bryan (<em>LJ<\/em>):<\/p>\n<p>Introduce your Linux distribution (the short, elevator-pitch version\u2014just<br \/>\na few sentences) and your role within it.<\/p>\n<p>Daniel (elementary):<\/p>\n<p>elementary is focused on growing the market for open-source software and<br \/>\nchipping away at the share of our closed-source competitors. We believe in<br \/>\nproviding a great user experience for both new users and pro users, and<br \/>\nputting a strong emphasis on security and privacy. We build elementary OS: a<br \/>\nconsumer-focused operating system for desktops and notebooks.<\/p>\n<p>My role at elementary is as Founder and CEO. I work with our various teams<br \/>\n(like design, development, web and translation teams) to put together a<br \/>\ncohesive vision, product roadmap and ensure that we&#8217;re following an<br \/>\nethical path to sustainable funding.<\/p>\n<p>Chris (Debian):<\/p>\n<p>The <a href=\"https:\/\/debian.org\">Debian Project<\/a>, which celebrated its <a href=\"https:\/\/bits.debian.org\/2018\/08\/debian-is-25.html\">25th birthday<\/a> this year, is<br \/>\none of the oldest and largest GNU\/Linux distributions and is run on an<br \/>\nentirely volunteer basis.<\/p>\n<p>Not only does it have stellar reputation for stability and technical<br \/>\nexcellence, it has a unwavering philosophical stance on free software (i.e., it<br \/>\ncomes with no proprietary software pre-installed and the <a href=\"https:\/\/www.debian.org\/vote\/2004\/vote_002\">main repository is<br \/>\nonly free software<\/a>). As it underpins countless derivative distributions,<br \/>\nsuch as Ubuntu, et al., it is uniquely poised and able to improve the Free<br \/>\nSoftware world as a whole.<\/p>\n<p>The Debian Project Leader (DPL) is a curious beast. Far from being a <a href=\"https:\/\/en.wikipedia.org\/wiki\/Benevolent_dictator_for_life\">BDFL<\/a>\u2014the<br \/>\nDPL has no authoritative or deciding say in technical matters\u2014the<br \/>\nproject leader is elected every year to a heady mix of figurehead, spokesperson<br \/>\nand focus\/contact point, but the DPL is also responsible for the quotidian business<br \/>\nof keeping the project moving with respect to <a href=\"https:\/\/lists.debian.org\/debian-devel-announce\/2018\/10\/msg00005.html\">reducing bureaucracy and<br \/>\nsmoothing any and all roadblocks to Debian Developers&#8217; productivity<\/a>.<\/p>\n<p>Matthew (Fedora):<\/p>\n<p>The Fedora distribution brings all of the innovation of thousands of upstream<br \/>\nprojects and hundreds of thousands of upstream developers together into a<br \/>\npolished operating system for users, with releases on a six-month cadence.<br \/>\nWe&#8217;re a community project tied together through the shared project mission<br \/>\nand through the &#8220;four Fs&#8221; of our foundations: Freedom, Friends, Features<br \/>\nand First. Something like 3,000 people contribute directly to Fedora in any<br \/>\ngiven year, with a core active group of around 400 people participating in<br \/>\nany given week.<\/p>\n<p>We just celebrated the 15th anniversary of our first release, but our history<br \/>\ngoes back even further than that to Red Hat Linux. I&#8217;m the Fedora Project<br \/>\nLeader, a role funded by Red Hat\u2014paying people to work on the project is<br \/>\nthe largest way Red Hat acts as a sponsor. It&#8217;s not a dictatorial role;<br \/>\nmostly, I collect good ideas and write short persuasive essays about them.<br \/>\nLeadership responsibility is shared with the Fedora Council, which includes<br \/>\nboth funded roles, members selected by parts of the community and at-large<br \/>\nelected representatives.<\/p>\n<p>Bryan (<em>LJ<\/em>):<\/p>\n<p>With introductions out of the way, let&#8217;s start with this (perhaps<br \/>\ndeceptively) simple question:<\/p>\n<p><em>How many Linux distributions should there be? And why?<\/em><\/p>\n<p>Daniel (elementary):<\/p>\n<p>As long as there are a set of users who aren&#8217;t getting their needs met by<br \/>\nexisting options, there&#8217;s a purpose for any number of distros to exist.<br \/>\nSome come and some go, and many are very very niche, but that&#8217;s okay. I<br \/>\nthink there&#8217;s a lot of people who are obsessed with trying to have some<br \/>\ndominant player take a total monopoly, but in every other market category,<br \/>\nit&#8217;s immediately apparent how silly that idea is. You wouldn&#8217;t want a<br \/>\nsingle clothing manufacturer or a single restaurant chain or a single<br \/>\ninternet provider (wink hint nudge) to have total market dominance. Diversity<br \/>\nand choice in the marketplace is good for customers, and I think it&#8217;s no<br \/>\ndifferent when it comes to operating systems.<\/p>\n<p>Matthew (Fedora):<\/p>\n<p>[Responding to Daniel]<br \/>\nYes, I agree exactly. That said, creating an entirely from scratch distro is<br \/>\na lot of work, and a lot of it not very interesting work. If you&#8217;ve<br \/>\ngot something innovative at the how-we-put-the-OS-together level (like<br \/>\nCoreOS), there&#8217;s room for that, but if you&#8217;re focused higher up the stack,<br \/>\nlike a new desktop environment or something else around user experience, it<br \/>\nmakes the most sense to make a derivative of one of the big community-powered<br \/>\ndistros. There&#8217;s a lot of boring hard work, and it makes sense to reuse<br \/>\nrather than carry those same rocks to the top of a slightly different hill.<\/p>\n<p>In Fedora, we&#8217;re aiming to make custom distro creation as easy as possible.<br \/>\nWe have &#8220;spins&#8221;, which are basically mini custom distros. This is stuff like<br \/>\nthe Python Classroom Lab or Fedora Jam (which is focused on musicians). We<br \/>\nhave a framework for making those <em>within<\/em> the Fedora project\u2014I&#8217;m all<br \/>\nabout encouraging bigger, broader sharing and collaboration in Fedora. But if<br \/>\nyou want to work outside the project\u2014say, you really have different ideas<br \/>\non free and open-source vs. proprietary software\u2014we have Fedora Remixes<br \/>\nthat let you do that.<\/p>\n<p>Chris (Debian):<\/p>\n<p>The competing choice of distributions is often cited as a reason preventing<br \/>\nLinux from becoming mainstream as it robs the movement of a consistent and focused<br \/>\nmarketing push.<\/p>\n<p>However, philosophical objections against monopolistic behaviour granted, the<br \/>\ndiversity and freedom that this bazaar of distributions affords is, in my<br \/>\nview, paradoxically exactly why<br \/>\nit has succeeded.<\/p>\n<p>That people are free\u2014but more important, feel free\u2014to create a<br \/>\nnew distribution as a means to try experimental or outlandish approaches to<br \/>\nperceived problems is surely sufficient justification<br \/>\nfor some degree of proliferation or even duplication of effort.<\/p>\n<p>In this capacity, Debian&#8217;s technical excellence, flexibility and deliberate<br \/>\nlack of a top-down direction has resulted in it becoming the base<br \/>\nunderpinning countless derivatives, clearly and evidently able to provide the<br \/>\ningredients to build one&#8217;s &#8220;own&#8221; distribution, often without overt credit.<\/p>\n<p>Matthew wrote: &#8220;if you want to work outside the project\u2014say, you really have different<br \/>\nideas on free and open source vs. proprietary software\u2014we have Fedora<br \/>\nRemixes that let you do that.&#8221;<\/p>\n<p>Given that, I would be curious to learn how you protect your reputation if<br \/>\nyou encourage, or people otherwise use your infrastructure, tools and possibly<br \/>\neven your name to create and<br \/>\ndistribute works that are antithetical to the cause of software and user<br \/>\nfreedom?<\/p>\n<p>Bryan (<em>LJ<\/em>):<\/p>\n<p><em>Thinking about it from a slightly different angle\u2014how many distros would<br \/>\nbe TOO many distros?<\/em><\/p>\n<p>Daniel (elementary):<\/p>\n<p>More than the market can sustain I guess? The thing about<br \/>\nLinux is that it powers all kinds of stuff. So even for one non-technical<br \/>\nperson, they could still end up running a handful of distros for their<br \/>\nnotebook, their router, their phone someday, IoT devices, etc. So the number<br \/>\nof distros that could exist sustainably could easily be in the hundreds or<br \/>\nthousands, I think.<\/p>\n<p>Chris (Debian):<\/p>\n<p>If I may be so bold as to interpret this more widely, whilst it might look<br \/>\nlike we have &#8220;too many&#8221; distributions, I fear this might be misunderstanding<br \/>\nthe reasons why people are creating these newer offerings in the first place.<\/p>\n<p>Apart from the aforementioned distros created for technical experimentation,<br \/>\nsomeone spinning up their own distribution might be (subconsciously!) doing<br \/>\nit for the delight and satisfaction in<br \/>\nbuilding something themselves and having their name attached to it\u2014something entirely reasonable and justifiable IMHO.<\/p>\n<p>To then read this creation through a lens of not being ideal for new users or<br \/>\neven some silly &#8220;Linux worldwide domination&#8221; metric could therefore even be<br \/>\nmissing the point and some of the sheer delight of free software to begin<br \/>\nwith.<\/p>\n<p>Besides, the &#8220;market&#8221; for distributions seems to be doing a pretty good job<br \/>\nof correcting itself.<\/p>\n<p>Bryan (<em>LJ<\/em>):<\/p>\n<p>Okay, since you guys brought it up, let&#8217;s talk about world domination.<\/p>\n<p><em>How much of what you do (and what your teams do) is influenced by a desire<br \/>\nto increase marketshare (either of your distribution specifically or<br \/>\ndesktop Linux in general)?<\/em><\/p>\n<p>Daniel (elementary):<\/p>\n<p>When we first started out, elementary OS was something we made for fun out of<br \/>\na desire to see something exist that we felt didn&#8217;t yet. But as the<br \/>\ncompany, and our user base, has grown, it&#8217;s become more clear that our<br \/>\nmission must be about getting open-source software in the hands of more<br \/>\npeople. As of now, our estimated userbase is somewhere in the hundreds of<br \/>\nthousands with more than 75% of downloads coming from users of closed-source<br \/>\noperating systems, so I think we&#8217;re making good progress toward that<br \/>\ngoal. Making the company mission about reaching out to people directly has<br \/>\nshaped the way we monetize, develop products, market and more, by ensuring<br \/>\nwe always put users&#8217; needs and experiences first.<\/p>\n<p>Chris (Debian):<\/p>\n<p>I think it would be fair to say that &#8220;increasing market share&#8221; is not an<br \/>\novert nor overly explicit priority for Debian.<\/p>\n<p>In our 25-year history, Debian has found that if we just continue to do good<br \/>\nwork, then good things will follow.<\/p>\n<p>That is not to say that other approaches can&#8217;t work or are harmful, but<br \/>\nchasing potentially chimeric concepts such as &#8220;market share&#8221; can very easily<br \/>\nlead to negative outcomes in the long run.<\/p>\n<p>Matthew (Fedora):<\/p>\n<p>A project&#8217;s user base is directly tied to its ability to have an effect in<br \/>\nthe world. If we were just doing cool stuff but no one used it, it really<br \/>\nwouldn&#8217;t matter much. And, no one really comes into working on a distro<br \/>\nwithout having been a user first. So I guess to answer the question directly<br \/>\nfor me at least, it&#8217;s pretty much all of it\u2014even things that are not<br \/>\nimmediately related are about helping keep our community healthy and growing<br \/>\nin the long term.<\/p>\n<p>Bryan (<em>LJ<\/em>):<\/p>\n<p>The three of you represent distros that are &#8220;funded&#8221; in very different ways.<br \/>\nFedora being sponsored (more or less) by Red Hat, elementary being its own<br \/>\ncompany and Debian being, well, Debian.<\/p>\n<p><em>I would love to hear your thoughts around funding the work that goes into<br \/>\nbuilding a distribution. Is there a &#8220;right&#8221; or &#8220;ideal&#8221; way to fund that work<br \/>\n(either from an ethical perspective or a purely practical one)?<\/em><\/p>\n<p>Chris (Debian):<\/p>\n<p>Clearly, melding &#8220;corporate interests&#8221; with the interests of a community<br \/>\ndistribution can be fraught with issues.<\/p>\n<p>I am always interested to hear how other distros separate influence and power<br \/>\nparticularly in terms of increasing transparency using tools such as Councils<br \/>\nwith community representation, etc. Indeed, this question of &#8220;optics&#8221; is<br \/>\noften highly under-appreciated; it is simply not enough to be honest, you<br \/>\nmust be seen to be honest too.<\/p>\n<p>Unfortunately, whilst I would love to be able to say that Debian is<br \/>\nby-definition free (!) of all such problems by not having a &#8220;big sister&#8221;<br \/>\ncompany sitting next to it, we have a long history of conversations regarding<br \/>\nthe role of money in funding contributors.<\/p>\n<p>For example, is it appropriate to fund developers to do work that might not<br \/>\nnot be done otherwise? And if it is paid for, isn&#8217;t this simply a feedback<br \/>\nloop that effectively ensures that this work will cease to within the remit<br \/>\nof volunteers. There are no easy answers and we have no firm consensus, alas.<\/p>\n<p>Daniel (elementary):<\/p>\n<p>I&#8217;m not sure that there&#8217;s a single right way, but I think we have the<br \/>\nopinion that there are some wrong ways. The biggest questions we&#8217;re<br \/>\nalways trying to ask about funding are where it&#8217;s coming from and what<br \/>\nit&#8217;s incentivizing. We&#8217;ve taken a hard stance that advertising income is<br \/>\nnot in the interest of our users. When companies make their income from<br \/>\nadvertising, they tend to have to make compromises to display advertising<br \/>\ncontent instead of the things their users actually want to see, and<br \/>\noftentimes are they incentivized to invade their users&#8217; privacy in order<br \/>\nto target ads more effectively. We&#8217;ve also chosen to avoid big enterprise<br \/>\nmarkets like server and IoT, because we believe that since companies will<br \/>\nnaturally be incentivized to work on products that turn a profit, that making<br \/>\nthat our business model would result in things like the recent Red Hat<br \/>\nacquisition or in killing products that users love, like Ubuntu&#8217;s Unity.<\/p>\n<p>Instead, we focus on things like individual sales of software directly to our<br \/>\nusers, bug bounties, Patreon, etc. We believe that doing business directly<br \/>\nwith our users incentivizes the company to focus on features and products<br \/>\nthat are in the benefit of those paying customers. Whenever a discussion<br \/>\ncomes up about how elementary is funded, we always make a point to evaluate<br \/>\nif that funding incentivizes outcomes that are ethical and in the favor of<br \/>\nour users.<\/p>\n<p>Regarding paying developers, I think elementary is a little different here.<br \/>\nWe believe that people writing open-source software should be able to make a<br \/>\nliving doing it. We owe a lot to our volunteer community, and the current<br \/>\nproduct could not be possible without their hard work, but we also have to<br \/>\nrecognize that there&#8217;s a significant portion of work that would never get<br \/>\ndone unless someone is being paid to do it. There are important tasks that<br \/>\nare difficult or menial, and expecting someone to volunteer their time to them<br \/>\nafter their full work day is a big ask, especially if the people<br \/>\nknowledgeable in these domains would have to take time away from their<br \/>\nfamilies or personal lives to do so. Many tasks are also just more suited to<br \/>\nsustained work and require the dedicated attention of a single person for<br \/>\nseveral weeks or months instead of some attention from multiple people over<br \/>\nthe span of years. So I think we&#8217;re pretty firmly in the camp that not<br \/>\nonly is it important for some work to be paid, but the eventual goal should<br \/>\nbe that anyone writing open-source code should be able to get paid for their<br \/>\ncontributions.<\/p>\n<p>Chris (Debian):<\/p>\n<p>Daniel wrote: &#8220;So I think we&#8217;re pretty firmly in the camp that not only is it<br \/>\nimportant for some work to be paid, but the eventual goal should be that anyone<br \/>\nwriting open-source code should be able to get paid.&#8221;<\/p>\n<p>Do you worry that you could be creating a two-tier community with this<br \/>\napproach?<\/p>\n<p>Not only in terms of hard influence (eg. if I&#8217;m paid, I&#8217;m likely to be able<br \/>\nto simply spend longer on my approach) but moreover in terms of &#8220;soft&#8221;<br \/>\ninfluence during discussions or by putting off<br \/>\nso-called &#8220;drive-thru&#8221; contributions? Do you do anything to prevent the<br \/>\nappearance of this?<\/p>\n<p>Matthew (Fedora):<\/p>\n<p>Chris wrote:<br \/>\n&#8220;Do you worry that you could be creating a two-tier community with this<br \/>\napproach?&#8221;<\/p>\n<p>Yeah, this is a big challenge for us. We have many people who are paid by Red<br \/>\nHat to work on Fedora either full time or as part of their job, and that<br \/>\ngives a freedom to just be <em>around<\/em> a lot more, which pretty much directly<br \/>\ntranslates to influence. Right now, many of the community-elected positions<br \/>\nin Fedora leadership are filled by Red Hatters, because they&#8217;re people the<br \/>\ncommunity knows and trusts. It takes a lot of time and effort to build up<br \/>\nthat visibility when you have a different day job. But there&#8217;s some important<br \/>\nnuances here too, because many of these Red Hatters aren&#8217;t actually paid to<br \/>\nwork on Fedora at all\u2014they&#8217;re doing it just like anyone else who loves the<br \/>\nproject.<\/p>\n<p>Daniel (elementary):<\/p>\n<p>Chris wrote:<br \/>\n&#8220;Do you worry that you could be creating a two-tier community with this<br \/>\napproach?&#8221;<\/p>\n<p>It&#8217;s possible, but I&#8217;m not sure that we&#8217;ve measured anything to<br \/>\nthis effect. I think you might be right that employees at elementary can have<br \/>\nmore influence just as a byproduct of having more time to participate in more<br \/>\ndiscussions, but I wouldn&#8217;t say that volunteers&#8217; opinions are<br \/>\ndiscounted in any way or that they&#8217;re underrepresented when it comes to<br \/>\nmajor technical decisions. I think it&#8217;s more that we can direct labor<br \/>\n<em>after<\/em> design and architecture decisions have been discussed. As an example,<br \/>\nwe recently had decided to make the switch from CMake to Meson. This was a<br \/>\ngroup discussion primarily led by volunteers, but the actual implementation<br \/>\nwas then largely carried out by employees.<\/p>\n<p>Chris (Debian):<\/p>\n<p>Daniel wrote:<br \/>\n&#8220;Do you worry that you could be creating a two-tier community with<br \/>\nthis approach? &#8230; It&#8217;s possible, but I&#8217;m not sure that we&#8217;ve measured anything to<br \/>\nthis effect.&#8221;<\/p>\n<p>I think it might be another one of those situations where the optics in play<br \/>\nis perhaps as important as the reality. Do you do anything to prevent the<br \/>\nappearance of any bias?<\/p>\n<p>Not sure how best to frame it hypothetically, but if I turned up to your<br \/>\nproject tomorrow and learned that some developers were paid for their work<br \/>\n(however fairly integrated in practice), that would perhaps put me off<br \/>\ninvesting my energy.<\/p>\n<p>Bryan (<em>LJ<\/em>):<\/p>\n<p><em>What do you see as the single biggest challenge currently facing both your<br \/>\nspecific project\u2014and desktop Linux in general?<\/em><\/p>\n<p>Daniel (elementary):<\/p>\n<p>Third-party apps! Our operating systems are valuable to people only if they can<br \/>\nuse them to complete the tasks that they care about. Today, that increasingly<br \/>\nmeans using proprietary services that tie in to closed-source and non-native<br \/>\napps that often have major usability and accessibility problems. Even major<br \/>\nopen-source apps like Firefox don&#8217;t adhere to free desktop standards like<br \/>\nshipping a .desktop file or take advantage of new cross-desktop metadata<br \/>\nstandards like AppStream. If we want to stay relevant for desktop users, we<br \/>\nneed to encourage the development of native open-source apps and invest in<br \/>\nnon-proprietary cloud services and social networks. The next set of<br \/>\nindustry-disrupting apps (like DropBox, Sketch, Slack, etc.) need to be open source and<br \/>\nLinux-first.<\/p>\n<p>Chris (Debian):<\/p>\n<p>Third-party apps\/stores are perhaps the biggest challenge facing all<br \/>\ndistributions within the medium- to long-term, but whilst I would concede<br \/>\nthere are cultural issues in play here, I believe they have some element of<br \/>\nbeing technical challenges or at least having some technical ameliorations.<\/p>\n<p>More difficult, however, is that our current paradigms of what constitutes<br \/>\nsoftware freedom are becoming difficult to square with the increased usage of<br \/>\ncloud services. In the years ahead we may need to revise our perspectives,<br \/>\nideas and possibly even our definitions of what constitutes free software.<\/p>\n<p>There will be a time when the FLOSS community will have to cease the casual<br \/>\nmocking of &#8220;cloud&#8221; and acknowledge the reality that it is, regardless of<br \/>\none&#8217;s view of it, here to stay.<\/p>\n<p>Matthew (Fedora):<\/p>\n<p>For desktop Linux, on the technical side, I&#8217;m worried about hardware<br \/>\nenablement\u2014not just the work dealing with driver compatibility and<br \/>\nproprietary hardware, but more fundamentally, just being locked out. We&#8217;ve<br \/>\njust seen Apple come out with hardware locked so Linux won&#8217;t even boot\u2014even with signed kernels. We&#8217;re going to see more of that, and more tablets<br \/>\nand tablet-keyboard combos with similar locked, proprietary operating<br \/>\nsystems.<\/p>\n<p>A bigger worry I have is with bringing the next generation to open<br \/>\nsource\u2014a lot of Fedora core contributors have been with the project since it started<br \/>\n15 years ago, which on the one hand is awesome, but also, we need to<br \/>\nmake sure that we&#8217;re not going to end up with no new energy. When I was a<br \/>\nkid, I got into computers through programming BASIC on an Apple ][. I could<br \/>\nsee commercial software and easily imagine myself making the same kind of<br \/>\nthing. Even the fanciest games on offer\u2014I could see the pixels and could<br \/>\nuse PEEK and POKE to make those beeps and boops. But now, with kids getting<br \/>\ninto computers via <em>Fortnite<\/em> or whatever, that&#8217;s not something one can just<br \/>\nsit down and make an approximation of as a middle-school kid. That&#8217;s<br \/>\ndiscouraging and makes a bigger hill to climb.<\/p>\n<p>This is one reason I&#8217;m excited about Fedora IoT\u2014you can use Linux and open<br \/>\nsource at a tinkerer&#8217;s level to make something that actually has an effect on<br \/>\nthe world around you, and actually probably a lot <em>better<\/em> than a lot of<br \/>\noff-the-shelf IoT stuff.<\/p>\n<p>Bryan (<em>LJ<\/em>):<\/p>\n<p><em>Where do you see your distribution in five years? What will be its place be in<br \/>\nthe broader Linux and computing world?<\/em><\/p>\n<p>Chris (Debian):<\/p>\n<p>Debian naturally faces some challenges in the years ahead, but I sincerely<br \/>\nbelieve that the Project remains as healthy as ever.<\/p>\n<p>We are remarkably cherished and uniquely poised to improve the free software<br \/>\necosystem as a whole. Moreover, our stellar reputation for technical<br \/>\nexcellence, stability and software freedom remains highly respected where<br \/>\nlosing this would surely be the beginning of the end for Debian.<\/p>\n<p>Daniel (elementary):<\/p>\n<p>Our short-term goals are mostly about growing our third-party app ecosystem and<br \/>\nimproving our platform. We&#8217;re investing a lot of time into online<br \/>\naccounts integration and working with other organizations, like GNOME, to<br \/>\nmake our libraries and tooling more compelling. Sandboxed packaging and<br \/>\nWayland will give us the tools to help keep our users&#8217; data private and<br \/>\nto keep their operating system stable and secure. We&#8217;re also working with<br \/>\nOEMs to make elementary OS more shippable and to give users a way to get an<br \/>\nopen-source operating system when they buy a new computer. Part of that work<br \/>\nis the new installer that we&#8217;re collaborating with System76 to develop.<br \/>\nOverall, I&#8217;d say that we&#8217;re going to continue to make it easier to<br \/>\nswitch away from closed-source operating systems, and we&#8217;re working on<br \/>\nincreasing collaborative efforts to do that.<\/p>\n<p>Bryan (<em>LJ<\/em>):<\/p>\n<p><em>When you go to a FOSS or Linux conference and see folks using Mac and Windows<br \/>\nPCs, what&#8217;s your reaction? Is it a good thing or a bad thing when<br \/>\ndevelopers of Linux software primarily use another platform?<\/em><\/p>\n<p>Chris (Debian):<\/p>\n<p>Rushing to label this as a &#8220;good&#8221; or &#8220;bad&#8221; thing can make it easy to miss the<br \/>\nunderlying and more interesting lessons we can learn here.<\/p>\n<p>Clearly, if everyone was using a Linux-based operating system, that would be a<br \/>\nbetter state of affairs, but if we are overly quick to dismiss the usage of<br \/>\nMac systems as &#8220;bad&#8221;, then we can often fail to understand why people have<br \/>\nchosen to adopt the trade-offs of these platforms in the first place.<\/p>\n<p>By not demonstrating sufficient empathy for such users as well as newcomers<br \/>\nor those without our experience, we alienate potential users and contributors<br \/>\nand tragically fail to communicate our true<br \/>\nmessage. Basically, we can be our own worst enemy sometimes.<\/p>\n<p>Daniel (elementary):<\/p>\n<p>Within elementary, we strongly believe in dogfood, but I think when we see<br \/>\nsomeone at a conference using a closed-source operating system, it&#8217;s a<br \/>\nlearning opportunity. Instead of being upset about it or blaming them, we<br \/>\nshould be asking why we haven&#8217;t been able to make a conversion. We need<br \/>\nto identify if the problem is a missing product, feature, or just with<br \/>\noutreach and then address that.<\/p>\n<p>Bryan (<em>LJ<\/em>):<\/p>\n<p><em>How often do you interact with the leaders of other distributions? And is<br \/>\nthat the right amount?<\/em><\/p>\n<p>Chris (Debian):<\/p>\n<p>Whilst there are a few meta-community discussion groups around, they tend to<br \/>\nhave a wider focus, so yes, I think we could probably talk a little more, even<br \/>\njust as a support group or a place to rant!<\/p>\n<p>More seriously though, this conversation itself has been fairly insightful,<br \/>\nand I&#8217;ve learned a few things that I think I &#8220;should&#8221; have known already,<br \/>\nhinting that we could be doing a better job here.<\/p>\n<p>Daniel (elementary):<\/p>\n<p>With other distros, not too often. I think we&#8217;re a bit more active with<br \/>\nour partners, upstreams and downstreams. It&#8217;s always interesting to hear<br \/>\nabout how someone else tackles a problem, so I would be interested in<br \/>\ninteracting more with others, but in a lot of cases, I think there are<br \/>\nphilosophical or technical differences that mean our solutions might not be<br \/>\nrelevant for other distros.<\/p>\n<p>Bryan (<em>LJ<\/em>):<\/p>\n<p><em>Is there value in the major distributions standardizing on package management<br \/>\nsystems? Should that be done? Can that be done?<\/em><\/p>\n<p>Chris (Debian):<\/p>\n<p>I think I would prefer to see effort go toward consistent philosophical<br \/>\noutlooks and messaging on third-party apps and related issues before I saw<br \/>\nenergy being invested into having a single package management format.<\/p>\n<p>I mean, is this really the thing that is holding us all back? I would grant<br \/>\nthere is some duplication of effort, but I&#8217;m not sure it is the most egregious<br \/>\nexample and\u2014as you suggest\u2014it is not even really technically<br \/>\nfeasible or is at least subject to severe diminishing returns.<\/p>\n<p>Daniel (elementary):<\/p>\n<p>For users, there&#8217;s a lot of value in being able to sideload<br \/>\ncross-platform, closed-source apps that they rely on. But outside of this use<br \/>\ncase, I&#8217;m not sure that packaging is much more than an implementation<br \/>\ndetail as far as our users are concerned. I do think though that developers<br \/>\ncan benefit from having more examples and more documentation available, and<br \/>\nthe packaging formats can benefit from having a diverse set of<br \/>\nimplementations. Having something like Flatpak or Snap become as well<br \/>\naccepted as SystemD would probably be good in the long run, but our users<br \/>\nprobably never noticed when we switched from Upstart, and they probably<br \/>\nwon&#8217;t notice when we switch from Debian packages.<\/p>\n<p>Bryan (<em>LJ<\/em>):<\/p>\n<p>Big thanks to Daniel, Matthew and Chris for taking time out to answer<br \/>\nquestions and engage in this discussion with each other. Seeing the<br \/>\nleadership of such excellent projects talking together about the things they<br \/>\ndiffer on\u2014and the things they align on completely\u2014warms my little<br \/>\nheart.<\/p>\n<p><a href=\"https:\/\/www.linuxjournal.com\/content\/state-desktop-linux-2019\" target=\"_blank\" rel=\"noopener\">Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A snapshot of the current state of Desktop Linux at the start of 2019\u2014with comparison charts and a roundtable Q&amp;A with the leaders of three top Linux distributions. I&#8217;ve never been able to stay in one place for long\u2014at least in terms of which Linux distribution I call home. In my time as a self-identified &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/www.appservgrid.com\/paw92\/index.php\/2019\/01\/01\/the-state-of-desktop-linux-2019\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;The State of Desktop Linux 2019&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-7046","post","type-post","status-publish","format-standard","hentry","category-linux"],"_links":{"self":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/7046","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/comments?post=7046"}],"version-history":[{"count":1,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/7046\/revisions"}],"predecessor-version":[{"id":7373,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/7046\/revisions\/7373"}],"wp:attachment":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/media?parent=7046"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/categories?post=7046"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/tags?post=7046"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}