8 ms·
System76: A Case Study on How Not to Collaborate with Upstream
- rob_c 5y agoMe wonders if the gnome his are aware of the further barriers to entry they're effectively creating by dragging up settled arguments. Not a fan of anything they've done recently under the gnome banner and don't see that changing too despite the IBM/RH money backing some of the project.
- TingPing 5y agoThis post is by one person, not GNOME.
- rob_c 5y agoYes, and my comment does not represent the entire non gnome community. My point is that the gnome devs are often acting a little precious to their idealised project and don't want to let control go. The fact so many distros ship with growing patchsets is proof to the problems in vanilla gnome.
- tebruno99 5y agoEh, I find it hard to relate to complaints when Gnome devs have spent the last 20 years treating users like they don’t know how to use a mouse & telling anyone Who wants to make it better that they are wrong.
- znpy 5y agoI was thinking something similar: on one hand system76 is probably wrong, but on the other hand gnome is trash and consistently screws up their users so... So happy I moved to XFCE (and i've been trying KDE lately).
- reginold 5y agoMLooks like this post won't play out well for Gnome. Plus System76 is building its own desktop environment in Rust.
- badsectoracula 5y agoThey also need to build their own toolkit (this one hopefully not in Rust or at least if in Rust with a C API that is accessible outside of Rust) because at this point Gtk is a vector for Gnomisms to projects outside of Gnome. Honestly IMO there needs to be a new toolit, one that understands the important of ABI stability over an actual long period of time (see Win32) and being easy to interface by a variety of different languages without having to spent ages for each interface. Gtk fails at the first, Qt fails at both.
- md8z 5y agoThey said they weren't going to do that and they would continue to use GTK. Also, this is wrong: "because at this point Gtk is a vector for Gnomisms to projects outside of Gnome." In GTK4 the goal has actually been to intentionally move GNOME specific bits out of gtk and into libadwaita. I can provide a source, if you want. "one that understands the important of ABI stability over an actual long period of time" I mean, I hear this asked for frequently but it's not clear what you want. You can keep using Qt 2/3, GTK 1/2 and those are technically "stable" but of course the trade off there is that you don't get new features, or bug fixes. So if you want someone to do something with those, it would help to ask for what you want specifically.
- badsectoracula 5y ago>Also, this is wrong: [..] "because at this point Gtk is a vector for Gnomisms to projects outside of Gnome." [..] In GTK4 the goal has actually been to intentionally move GNOME specific bits out of gtk and into libadwaita. I can provide a source, if you want. I do not see it as wrong, Gtk and GNOME developers have said a lot of stuff over the year but at the end of the day it is what they do that matters and ever since Gtk3 they basically took over Gtk. > I mean, I hear this asked for frequently but it's not clear what you want. How is it not clear, i explicitly provided Win32 as an example right after the part you cut at. After all... > You can keep using Qt 2/3, GTK 1/2 and those are technically "stable" but of course the trade off there is that you don't get new features, or bug fixes. ...Win32 does get new features and bug fixes all the time - even the pre-XP controls (i mean the non-themed common controls) still get updates. Qt 2/3 and Gtk 1 (not Gtk 2 so far though) aren't realistic targets either as you can't make a binary and expect it to be available anywhere - except perhaps Slackware which still distributes Gtk 1 (i do not think it distributes Qt 2 or 3 though). So you have to bundle the libraries with your application (**please** do not compare this with Windows, Windows come with a A TON of stuff you can rely to be there even if you do not use it - like a GUI toolkit for example... actually a bunch of GUI toolkits, but let's stick with Win32 which is what i originally brought up) which not only bloat the application itself but also version lock the dependencies to whatever you bundled, including its features and bugs. So for example a Gtk2 or Qt 2 or Qt 3 application (and perhaps a Qt 4 application too, though not 100% sure) might work but, e.g., it wont get a Wayland backend because the bundled version you have was never updated for it. It also wont get high DPI support for the same reasons. If you bundle Gtk3 or Gtk4 or Qt 5 now and someone finally implements per-monitor window events under X11 for scaling like in Windows which also requires toolkit support, your application wont support those because instead of using the system bundled libraries, you use your own. If some distribution decides that enough is enough and implements a better file dialog for Gtk again your application wont get the new functionality because instead of using the distribution's libraries you use your own. Etc. What i want is simple: a stable ABI so that binary applications can keep working in future (think timeframes of 20, 30 years and more, not just a couple of years or whatever) while getting new features whenever that is technically possible with the same binaries, a stable and backwards compatible API so that source code can still be compiled as-is in the future (or at least the library wont be the reason it wont be compilable) while still getting new features for applications that are still in active development to use so that they look, perform and behave better but without forcing everyone to upgrade in a step-lock but instead letting them do that whenever they can (and assuming they even need the updates - let applications where these updates do not matter for keep using the existing APIs), any documentation, be it first party or third party, that was written over the years wont be invalidated and the invaluable and limited time of documentation writers wont be wasted and instead be used on new stuff where that matters, the knowledge of those who bothered to learn the library wont be invalidated, application developers who spent time targeting the library wont have to waste time re-do things that they've already done just to get more or less the same result, etc. See OpenGL as an example: now OpenGL has gained bad rep over the recent years (and i personally blame Khronos over its mismanagement) but regardless, a Windows application that was written back in the late 90s using the OpenGL 1.1 API worked on GPUs of the time that usually all they could do was triangle rasterization and everything else was done on the CPU. Then the exact same application, same EXE file, could run on a later GeForce 2 TI that implemented many parts of the API in hardware. Then nowadays, the exact same application, same EXE file, can run on a modern GPU that got rid almost all of the fixed function hardware but still implements the same API largely in shaders - but the program works and has better performance than it ever did, even if it doesn't have the best performance it could have. But even better, it can get functionality like MSAA support from the drivers, triple buffering, vsync control, etc that didn't exist at the time. What is more, if the source is still around, chances are it can be recompiled as-is (or at least the OpenGL bits could) and its functionality be extended by adding additional code alongside the existing code to use new features like shaders. In fact this is what Beamdog did with Neverwinter Nights: Extended Edition where the original game was written against OpenGL 1.x but they - almost two decades later - started adding additional functionality to the game (but the original game still works fine). What i ask isn't fantasy, it is something other APIs have done, including the Win32 API (at least the GUI bits) which pretty much offers what a toolkit offers in Linux.
- md8z 5y agoJust FYI. If your suggestions for "making it better" for yourself would be making it worse for other users, then that probably would be why your suggestions weren't taken. GNOME has made accessibility a priority for a while now, so that is why the interaction with the mouse has been done the way it is. (Disclaimer: I am not a GNOME developer, this is just my observation)
- p_l 5y agoMore than once the suggestions weren't breaking accessibility at all, and at least once it was GNOME devs deciding unilaterally that they know better than users who will face accessibility issues due to their changes.
- md8z 5y agoCan you please give an example? Keep in mind that if a change fixes some accessibility issues for some people but then causes other accessibility regressions elsewhere, that could also be bad and not wanted. Nobody wants to be the person to make that decision and deal with the angry users, but sadly, somebody has to do it unilaterally otherwise development on the project will not happen. Really now, if your stance is "it is bad for an open source maintainer to make decisions that might be difficult" then it seems you would have trouble finding any project that suits you.
- p_l 5y agoForcing single IME state globally and attempting to remove even the possibility of using per-window/application state in IBus. Mind you, this was removing the option, those who preferred single global state already could do so. The argument was that it would lower cognitive load, without any evidence backing it up, and obviously with no input from people who regularly have to mix different input systems - where the ability for IME state to match context of the window they are in, especially as sometimes the different tasks in different windows would have incompatible needs on current IME state.
- 5y ago
- MadcapJake 5y agoThe vitriol thrown at Gnome devs has always been a needed reminder that engineers are just as capable of falling for a surface-level and biased narrative as the average American. The fact that many of the Gnome maintainers still continue to develop the Gnome ecosystem is a bonafide miracle. The one grain of truth in this mess is that many diehard desktop users don't want innovation, they want the traditional 00s style desktop. MATE, Cinnamon and XFCE serve that crowd swimmingly so can we stop with the hate?
- AtlasBarfed 5y agoLinux has taken over the server space. But Linux can't even keep up with OSX in market share, or more importantly, developer effort for games/apps/etc. So Gnome should ask itself after about two decades... are they helping or hurting. KDE should ask itself a similar question. Gnome has several active Gnome2 forks out there and Gnome3, KDE is simply ... ok And even then, Unity was another attempt, and who knows what ChromeOS is built on. Linux already pissed away the golden opportunity of Windows 8. Now that Apple is leading an ISA shift from x86 to ARM on the desktop, Linux needs to get its desktop situation ready. Linux and OSS are uniquely positioned to outclass Windows in the ISA move, arguably they are in a better position than OSX was in the M1 move. A huge portion of its applications can simply be ported with a decently supported recompile and I think there are package infrastructures that will well support an ARM ISA changeover. The issue is the desktop. The blocker is the desktop. The barrier is the desktop. I welcome System76 to take no prisoners in this critical period. If they fail, well, oh well. If they push Gnome/KDE to keep up out of paranoia, well, good. Just please people, please. Windows is awful. OSX is becoming a jail.
- reginold 5y agoWhat do you think of System76 developing their own desktop environment? HN post: https://news.ycombinator.com/item?id=29137180 https://news.ycombinator.com/item?id=29137180
- tebruno99 5y agoSounds cool. If they can fund it & have fun doing it could be neat. All desktops started at Zero and competition will drive others to stay ahead or fall behind
- md8z 5y agoI don't think this is going to help at all. There are already way too many desktops for Linux and none of them are pushing GNOME or KDE to keep up. To me this is just another one to add to the pile sadly. We already went through this whole song and dance with Canonical and Unity and that ended up dead as well. ChromeOS (and Android) are their own things and not related to any of the other projects. If somebody was building a new desktop and had a few hundred million dollars to spare I would say just do that similar to how Google did it. A company with those resources would be wasting them by involving itself with the open source desktops, those projects are perpetually in a state of being 5-10 years behind. Of course that means they would have to bring their own app ecosystem too.
- theamk 5y agothat's alarming! They give examples where PopOS should have worked with upstream... they are youtube-dl breaking [0] -- the bug was open for 21 days before maintainer fixed it... once it was fixed, it took about 10 more days to propagate to older releases. And this was for the script whose only purpose was to interact with 3rd party websites -- it makes no sense to use older versions, they likely won't work at all! nvidia lid closing problems [1]: bug reported 2017-11-05 and includes ready to apply patch. 2019-06-11, more than 19 months later, system76 mentions the patch is not applied and recommends PopOS... only then maintainers notice this and fast-track into Ubuntu. Not sure who is right there, but they are really not making the case for working with upstream. [0] https://bugs.launchpad.net/ubuntu/+source/youtube-dl/+bug/1831778 https://bugs.launchpad.net/ubuntu/+source/youtube-dl/+bug/18... [1] https://bugs.launchpad.net/ubuntu/+source/youtube-dl/+bug/1831778 https://bugs.launchpad.net/ubuntu/+source/youtube-dl/+bug/18...
- tomnipotent 5y agoI read this expecting to pooh-pooh on System76, but left thinking maybe they have a good case. At heart are some opinionated changes by the libadwaita team to disable global styling, which align with an anti-theming petition that some of the team members support (stopthemingmy.app). These decisions wouldn't normally be particularly noteworthy, except that libadwaita seems posed to make its way into "core" GNOME software and would thusly affect System76 and their own efforts in customizing Pop_OS!. Some of the S76 staff responses are brash, but not without merit. I'm left with the impression that distros are not considered a "customer" by these GNOME contributors, so much as the app developers in their immediate circles that shoulder the brunt of support issues caused by the problems they hope to solve.
- md8z 5y agoThe amount of misinformation on the net about theming in libadwaita is staggering. Global styling hasn't been disabled. There is nothing there that would really affect them in any significantly worse way than GTK3. That isn't to say they should do it, CSS theming will still be as broken and ill-advised as it is in GTK3, you can see that with the images at the bottom of the article. "which align with an anti-theming petition that some of the team members support (stopthemingmy.app)" To me this is a bad way to put it. I don't consider myself to be "anti-theming" and I agree with everything in that petition, except for the title which seems to be inflammatory and has contributed to some of the confusion and upset about theming in GTK. The title could be changed and the petition would be much better, I think. But it is probably too late for that.
- tomnipotent 5y ago> Global styling hasn't been disabled But that's the plan, while working on a recoloring API leading up to Gnome 42 when libadwaita can be adopted into core apps.
- md8z 5y agoIt's not the plan though. You can still inject global styles into libadwaita apps. It continues to be as bad an idea as it was before. I'm happy to provide details here.
- volta83 5y ago> System76 & the LVFS > [...] > Later on the LVFS team put in work to support the use case of System76 so that vendors could use the LVFS without any sort of reporting. > https://archive.is/mH4dO https://archive.is/mH4dO The goal of the author here is to show how bad System76 behaved. But after reading this, clicking the links, and reading the PR that actually got implemented (link above) my take is that System76 had to fight for years to get an option added to fwupd, to avoid their users from getting tracked when downloading system76 firmware through the tool. That... doesn't sound like evil to me? I didn't knew that fwupd collects statistics about which firmwares my laptops download, from where, when, etc. and sends them to the hardware vendors. Is there a way for users to disable this tracking for all firmwares from all vendors? If anything, this actually makes me want to get a System76 laptop.
- esarbe 5y ago> my take is that System76 had to fight for years to get an option added to fwupd, to avoid their users from getting tracked when downloading system76 firmware through the tool. Well, no. They didn't 'fight' for that, they complained about it. For a while they decided that LVFS wasn't a right fit and went with their own tool and infrastructure[0]. To quote: " I then got told that I’d made the LVFS and fwupd more complicated than it needed to be, and that I should have adopted the infrastructure that System76 had built instead. This was all without them actually logging into the LVFS and seeing what features were available or what constraints were being handled." [1] But they didn't 'fight' for it. Richard Hughes fought for it. And even more than that; he implemented it, which is what counts. > That... doesn't sound like evil to me? Well, no. Spreading FUD on the other hand could be considered - if not evil - then at least somewhat mean[2] > If anything, this actually makes me want to get a System76 laptop. That's awesome. We need more people buying custom Linux hardware. The more, the merrier, the lower the costs, the better the support. [0] https://archive.md/VPvhu https://archive.md/VPvhu [1] https://archive.md/A4ZMS https://archive.md/A4ZMS [2] https://archive.md/UgGxn https://archive.md/UgGxn
- volta83 5y ago> Well, no. They didn't 'fight' for that, they complained about it. For a while they decided that LVFS wasn't a right fit and went with their own tool and infrastructure[0]. So why is this a problem ? If LVFS isn't a right fit, cause its missing a feature, and they prefer to roll their own system instead of submitting a 100 LOC patch, that's kind of up to them ?
- COGlory 5y ago... this only lessens my opinion of Gnome. What ridiculous self righteousness
- esarbe 5y agoI think they make a fairly good point about when and how communication between the developers broke down. That exactly did you find 'self righteous' about it?
- alpanka 5y agoCome on people, it's not like gnome devs are masters of collaboration themselves. Gnome designers can come up with a new direction that 99% of their users hate and they wouldn't even care. Most recent releases have basically been "let's remove something everyone love and use every day, because we can". For example, they removed desktop icons and redesigned the dash to be big and ugly and always autohide and made display overview horizontal with no way to change back. Ubuntu is using old gnome releases because if they upgraded to the last release half their paying customers would leave in anger.
- md8z 5y agoThat is a misconception. The GNOME designers I have seen are not making decisions at random or removing things because they can, there actually is data and research to back up what they are doing. If you are a designer and are interested to know more then it would benefit to talk to them and ask them for their reasons, and then maybe you could contribute meaningfully from that angle. If there is something you think they missed, and you have the data to back it up (i.e. real usage data over long periods of time from large groups of users), then I think that would be helpful.
- ekianjo 5y ago> there actually is data and research to back up what they are doing. Oh really? There was data to back up that users wanted to start their desktop in Overview mode instead of the usual desktop? I'd be SUPER interested to see what kind of bullshit data was used, if this data ever exists. Right after this happened people created an extension to backtrack on this and this is one of the most popular extensions on GNOME extensions.
- md8z 5y agoYes, there was data to decide that, you should ask them nicely on the proper channel if you want more info. Please avoid dismissing things as "bullshit", that's rude and it doesn't help the discussion. If you have any additional data to the contrary, then now would be the time to present it. AFAIK extensions are considered as a data point but are not the only one, any time there is a design change there tends to be an extension that reverts it so it's not much of a reliable thing.
- transportheap 5y agosystem76 isnt alone, openbsd devs and packagers regularly also dont share with upstream too. they even got caught so they change their policy on sharing https://marc.info/?t=160764244000001&r=1&w=2 https://marc.info/?t=160764244000001&r=1&w=2
- phendrenad2 5y agoYou mean they got "caught" breaking their own policy, which they imposed on themselves, and they didn't break any copyrights?
- phendrenad2 5y agoI don't get all of the hostility against GNOME. If you don't like it... use something else? System 76 has been trying to have their cake and eat it too, using GNOME but not jumping through all of the GNOME hoops. I guess the latest new is they're going to get away from GNOME and make their own DE, which is great news for all involved.
- Jnr 5y agoI agree that those are great news that someone is making a new DE. But currently switching away from Gnome is not that simple, especially if you dislike KDE. A lot of work is being put into making Wayland usable, and a lot of interfaces for features that everyone expects from a modern computer don't really exist outside of Gnome and KDE yet. As I see it, a lot of users are not forced to use Gnome, but because of their dominance, there aren't many modern mature alternatives to it. I am a Gnome user myself and with every single update lots of extensions break. Without those extensions I can't really use Linux Desktop efficiently. What would you say if your browser extensions got broken with every browser update?
- Jnr 5y agoI have not seen a distribution where updating Gnome wasn't an issue. I hope that System76 is serious about their DE, and that if their development approach is more inclusive and better planned, other distributions will follow them. In my opinion Gnome is a big reason why Linux Desktop is struggling to gain traction. It is not friendly to people migrating from other OS (the features are not there without tons of extensions) and it is not friendly to app and extension developers (things break after every small update and Gnome and GTK documentation is terrible). People should stop expecting that Gnome will improve in those fronts, and similarly as Wayland is replacing Xorg, something better should replace the Gnome and gnome-shell desktop experience.
- culopatin 5y agoI just installed fedora and I agree. Why would I want my whole screen to shrink everything every time I want to do something? I can’t even open an app without all the stuff shuffling around and back. Why can’t I see the dock when I bring my cursor to the bottom of the screen? Oh wait I have to go all the way up there to activities to see it. What windows do I have open? Oh wait I gotta go to activities again. How do I minimize something? Idk, no button. Double click? No that’s just maximize. I guess I can only close stuff. It’s almost like someone decided that we needed yet another “way “ of doing things instead of conforming to what people are used to.
- raffraffraff 5y agoWow. I didn't realise things were that bad. I stopped trying out other DEs years ago. I quit KDE after the v4 trash fire (2008), quit Gnome after v3 (2011) and had a year long affair with Openbox (nice, but needs too much work to get basics working). I settled down with XFCE about 7 years ago and never looked back (or forward). Nothing is perfect, but at least XFCE doesn't wreck my flow after an upgrade, and I can script most things I care about and attach them to keyboard shortcuts or triggers.