• 0 Posts
  • 18 Comments
Joined 2 years ago
cake
Cake day: July 16th, 2023

help-circle


  • I was intrigued by XFCE on Wayland so I looked into it.

    XFCE is not really available on Wayland yet. XFWM is X11 only and there is no XFCE compositor.

    What Leap is doing is running the XFCE panel and apps on Labwc. When I have tried this, “it works” but it is certainly not as polished as XFCE on Xorg.

    I am a Wayland fan so overall I support OpenSUSE moving to Wayland. This seems like a bit of disservice to XFCE fans though as I am not sure the DE is ready yet. And the take-away is going to be that it is Wayland that is not working.


  • Sadly, it is a detachment from reality that is entirely normal, even typical. In all walks of life.

    What I still find surprising, even though normal, is how technical people can push actual facts and evidence right out of their world view.

    Sure, 70% of the bugs in C++ code bases are memory rated according to multiple sources. So let me aggressively and confidently berate this idiot that says the Rust compiler is doing something useful.

    You do not have to use either language to see how idiotic this is. Even if you accept that this guy has “the skill” to make compiler help redundant, he has no point at all unless he thinks that “typical” C++ users have that same level of skill. And, provably and trivially researched—they do not. Being this wrong makes him, as self-evidenced, incompetent by definition.

    All he proves in the end is that he is angry (and I guess not a fan of Rust).

    “Angry and incompetent” is sadly a much more common trope than the ones he tires off.


  • Disparagated? I assume you mean disparaging but that does not really track to the copium comment.

    I know I am coming off a bit harsh. I am just tired of Xorg fans going off about how Wayland is not ready when it is already the most popular desktop Linux display server.

    I don’t like systemd but I would not be expected to be taken very seriously if I wrote an article saying that people will never use it when 90% of Linux desktops are systemd based.

    Or perhaps in should write an article about how nobody clang is not ready because I have a use case it does not fit.

    And the list of things that Wayland can do that Xorg cannot is longer than the reverse at this point. So, a list of things you prefer about Xorg is just a personal preference at best at this point. Trying to argue that Wayland is “not ready” when it is both more advanced and more popular should be called out for what it is.

    Shouting that the guy crossing the finish line ahead of you does not stand a chance just sounds stupid. And that is what this article is doing.



  • It is a well known risk but not something that was a real risk numerically. I mean, it still isn’t given the number of packages in the AUR.

    This is a couple of malicious packages discovered in a short period though. Not a good sign. It was really impact the AUR if polluting it with malware became common.

    You should always inspect AUR packages before installing them but few people do. Many would not even know what they were looking at.


  • I have Linux on:

    • 2013 MacBook Air
    • 2017 MacBook Air
    • 2021 MacBook Air
    • 2009 MacBook Pro
    • 2012 MacBook Pro
    • 2008 iMac
    • 2015 iMac
    • 2013 Mac Pro

    I predict that EndeavourOS will run beautifully on your 2014 MacBook Air. You need out-of-kernel drivers for both the Broadcom WiFi and the FacetimeHD camera but EOS has you covered on both. They will both update automatically when you update the kernel. EOS has much faster WiFi on my 2013 than the other distros I have tried. Chimera Linux works beautifully as well but that may not be your scene.

    I have not tried Mint on any of the hardware above so unfortunately, I cannot say how well it would work. Perhaps just fine though I wonder about the webcam.

    As you guessed, installing Linux on that hardware is just holding down the Option key to boot of the USB. It is pretty close to regular PC hardware with a slightly odd UEFI. Everything works, even all the media keys, brightness control, etc.

    You can use OpenCore Legacy Patcher to put a newer version of macOS on that hardware as well. As you can tell though, I think Linux is the better play. You will be amazed at how well the 2014 runs.

    [edit: I just read some of the other comments. I never had any of those issues with EOS. I really recommend it for that hardware.]


  • Mint is awesome. There is absolutely nothing wrong with using Mint on Xorg today. I converted somebody to Linux recently and I put them on Mint (X11). There are not that many Wayland only apps yet. And if you don’t use them yet, you won’t miss them.

    Please just don’t post “Wayland is not ready” articles because Cinnamon is not ready (does not fully support Wayland yet).

    Cinnamon will go Wayland though. When they are ready, they will switch you over. At some point, they will drop support for Xorg.


  • Remind me 2030 if these issues I have get fixed:

    You want me to track the progress of 4 bugs in Sway? Such a powerful argument. How about don’t use Sway?

    One issue the wayland proponents fail to notice is that the ecosystem itself is fragmented

    I did not fail to notice. I have another post here comparing compositors to web browsers. There is more than one by design. Long term, it is absolutely one of Wayland’s strengths. But ya, your experience is only going to be as good as the browser you choose.

    For tiler lovers, Niri and Hyprland are both great. COSMIC is looking good but still Alpha. Plasma 6 is perhaps the best Wayland compositor at the moment.

    why don’t you stop using linux and move to windows?

    Hilarious. Linux has been my primary desktop since the 90’s. You probably need to get off my lawn.

    https://aur.archlinux.org/packages/12to11-git

    Even more hilarious. Looks like you found an even crappier Wayland compositor than Sway.

    Amongst the long list of broken things in 12to11, my favourite is this: “has not been tested on window (and compositing) managers other than GNOME Shell”. GNOME is a Wayland first and soon to be Wayland only project. A project clinging to Wayland on X on GNOME is a perfect metaphor for the point I am making. Thank you for making my point so well.

    By 2030, Xorg will be in the AUR and the only x server in the core Arch repos will be Wayback (Xwayland on Wayland).

    Sounds like you will be using 12to11 to run Wayland apps on i3 on XWayland on Wayback (Wayland on X on Wayland). Good times.

    You seem to think I am telling you to use Wayland though.I don’t care what you use. My point is that everybody else is happy leaving you behind. Keep using X. You can switch to the Dillo browser too if you want. LMAO.

    Very subtle “Arch, BTW”, BTW. Nice.

    For everybody else, here is the project you linked to. It is a fun little project.

    https://git.linuxping.win/12to11/12to11


  • Here is an argument that some of the grumpy old men clinging to Xorg may understand.

    It is 2003 and all the cool kids are moving to this new web browser called Firefox. But every time you try your favourite websites in it, you find stuff that breaks. So back to trusty old Internet Explorer 6 you go. Call me when it works you say.

    Wayland is like HTML. Wayland compositors are web browsers. And yes, all these “modern” web standards are all implemented a little differently or maybe not at all in some browsers. And, annoyingly, a lot of real world websites still work better in Internet Explorer 6 than in any of these supposedly “modern” browsers.

    But, as with the web, it will not be long until all websites (Linux desktop applications) will be written to use the modern standards and will work well, and pretty much the same, in all browsers (Wayland compositors).

    And, while there will still be websites (Linux desktop apps) that work better in IE6 (Xorg), most people will consider those sites broken and will probably not use them. Alternatively, you can run your browser (compositor) in compatibility mode (Xwayland) for those sites.

    You can keep using Internet Explorer if you want. Many people held on for a long time. Just know what your advocacy sounds like to people that have moved on to Firefox and Chrome. Pointing at your corporate website that looks wrong in Firefox will not impress them. And understand that you will not be able to hang on forever. Well, unless you want to be stuck in a tiny corner of the web that still works on your browser. Most websites will stop working on Internet Explorer at some point.




  • These “Wayland will never come” articles completely ignore the fact that Wayland is here and has already won.

    There are lots of issues with Wayland. They will be fixed, but if this was simply a list of things still needing to be improved, it would be useful.

    But most Linux desktop users use Wayland already. It will be 90% in 2-3 years. With the exception of Mint, the big Linux distros already install to Linux by default. So almost every new Linux user starts on Wayland. Few will ever try X11. And if they did, the list of broken and impaired experiences on X11 will bring most back to Wayland.

    It really does not matter if every x11 user switches to Wayland. The ecosystem does not need them.

    But very few of even the hard core adherents will use an X server 5 years from now. Most normal users will not even use Xwayland. And the simple reason is applications.

    Everyday there are more and more apps that are Wayland only. Before 2030, that list will include all GNOME and most GTK apps. Are people really going to give up all these applications because of some obscure advantage they perceive in X11?

    Most the the faults the article cites are exaggerated or historical. But it is not worth arguing over the details. Wayland is the future. But it is already the present. It is sad really that the people writing these articles do not realize that they are already in the minority and have already been left behind.

    This is a “Linux will never be ready for all UNIX users” article written in 1998. It is both true and irrelevant.



  • Regardless of your stance on GPL or not, I find the firmware stance very strange.

    If software is made available to you, you must reject it. But as long as the hardware runs it behind closed doors, you can use it.

    The CPU microcode situation is a good example. You can run your CPU, having no idea what it is doing or how it works. No problem. But if they ship an update to fix a bug, you cannot apply that update unless it is open source. The “free” choice is to run known vulnerabilities on top of the black box. And the in-chip behaviour is complex enough that Intel chips included a whole UNIX-like operating system in them (Minix) and people did not even realize it. The same is true for every chip in your system. Crazy.

    If you are not going to demand open hardware, there is no point in being so absolutist about the firmware. That is even if you want to be truly hard core about the software running on top.