I’ve only ever found a use for sed once two decades into my career, and that was to work around a bug due to misuse of BigInt for some hash calculations in a Java component; awk remains unused. Bash builtins cover almost everything for which I find those are typically used.
If you're using find all the time, check to see if you have or can have some variant of locate installed. It indexes everything* on the system (* this is configurable) and can be queried with partial pathnames, even with regex, and it's fast.
Then why is this piece of shit called x11’s successor or even x12? Why do you want to force adoption of this 2 decade long unfinished beta software when it can’t even run most applications?
Also, the red hat moderators have banned my previous account as expected. They are literally moderating many forums like reddit’s linux subreddit and this place, and enforce censorship. They banned my account for posting the github gist posted in the OP. I didn’t even break any rules, they indiscriminately banned me just because i posted one post portraying wayland in a negative light.
Because it is the replacement for Xorg and X11 as a whole. This is like expecting all Unix applications to work on Linux. No, some things need to be ported or rewritten. I don’t want to force adoption of Wayland. Heck, I’m on Xorg because Qtile’s Wayland session is missing a thing or two I need (they’re in development but not there yet). I’m just tired of people pretending this article is accurate and up to date so I wanted to set some things clear. Granted, I didn’t do it that well, but I tried.
Also, whoever calls Wayland X12 is lying to themselves and everyone else. The only way in which such naming would make sense is if you consider the fact that the X11 maintainers (pretty much all of them RedHat employees) were sick and tired of maintaining it, so they started Wayland to replace X11 (NOT as a drop in replacement, mind you). So the only way such naming wpuld make sense is if you consoder the fact that Wayland developers and maintainers were the same people that were maintaining Xorg until they just gave up.
Some people including myself call Wayland X12 because Wayland is a subset of the X12 protocol made by the X11 maintainers, and as such is as close to an X11 successor as you can get.
Because the people who developed X11 (that is Xorg) haven declared that. Maybe they should have named it X12, but they didn't for whatever reason. However the people doing the work have already given up on working on X11 they gave up on X11 beyond the bare minimum almost 10 years ago because some real issues with X11 as a protocol are not fixable.
There were other attempts to a successor to X11, but they never got the support of people doing the work on X11 (in part because they didn't understand the problem with X11 and so kept many bad things while 'fixing' things that were not broken)
Which is to say: you have two choices: get involved with continuing X11 development, or jump to Wayland. Throw a couple million $$$ per year at X11 (either pay developers, or convince a dozen developers to maintain X11) and I'll retract my statement, until then X11 is dead. If you cannot do that then Wayland is your only option.
In the case of Waydroid, it depends on features only available in Wayland; simple as that.
There are some applications (like autoclickers) that depend on features only available in X, as well (mainly because they directly ask X to do something)
Judging by post & history. They are just a troll. As for this article. I don’t understand why anyone bothers sharing it. It is one of the most hot garbage ones I have seen. Most of this article gives arguments that are either old, have no relevance here or are just plainly cherrypicked (the jitsi one for example, open the link and see the last comment, that they quoted). Most things are also application side issue with no relevance for wayland devs. “Oh my app does not work in wayland? Must be wayland’s fault!” This is a rubbish logicless argument. If one wants to not use Wayland, they are welcome. But things like “Boycott Wayland” are irritating to those who do want to use Wayland because they know how Xorg is.
How about an example of Wayland forcing me to use GNOME like this rant alleges? I hate GNOME but have been using KDE with Wayland for like two years now.
Same. Not to mention that there’s window managers in development if people prefer that. Some examples I know include Sway for those who want something like i3, Wayfire for those who miss Compiz and Hyprland for a more polished tiled experience. Hyprland in particular I’d recommend as I’ve personally had no luck with X.org compositors like Picom - didn’t work with my GPU.
The one that bother me the most about Wayland is the future of *BSD desktop. Can you run Wayland on NetBSD/FreeBSD yet? Also, currently you can run x server on Mac so you can run X11 apps remotely for example. Is there any attempt to make waypipe work on MacOS?
It’s been working for a while unless I’m misunderstanding what you mean by screen capture. But I’ve been using OBS on KDE Wayland capturing via portals for months now with issues.
I just tried it. Create a “Screen capture (PipeWire)” source, there’s a popup asking you to pick a display or “Full Workspace” which shares everything.
There really isn’t one. Wayland is maturing and app support is following.
This is the way things always go in open source. I’m betting soon there will be a distro that will announce a never Wayland stance just like Devuan prior.
this is probably actually the fault of wayland and it’s fragmentation issue. Various wayland compositors have different methods of interacting with them and this includes remote/virtual input. Because of this fragmentation a lot of developers have just started to kinda give up, on wayland.
for this one specifically, I would assume any virtual input would work? there are a couple possible routes forwards, the easiest is probably using XDG’s RemoteDesktop. However not every compositor implements this, Sway will be getting it soon (or already has it using luminous). There are also numerous compositors that don’t support this.
you have wlr-virtual-{pointer,keyboard} which works on sway and mir, and thats it. I believe there was a compositor that could do this over dbus too?
the reality of wayland is, if it’s not in the core protocol, you aren’t guranteed to have support, and if it is in the core protocol, you still arent guranteed to have support, but the chances are better
So, it turns out that my RMM is working fine under Wayland. Level got back with me because they couldn’t reproduce the problem. So I tried to reproduce the problem. Only to find it is working just fine. Whatever was causing that problem, I have no idea. But it’s gone.
interesting, do you know what they were using for input? if they have an encompassing solution that could be great. if they just use xdg remotedesktop, well thats about what I have now anyways T.T
Timeshift forces you to use a very specific layout of btrfs partitions or whatever those are called. On Fedora.for instance, unless you set them up manually, Timeshift will not work. Snapper isn’t so picky.
I never had to set it up. I use endeavour OS and all I did was choose “btrfs” in the installer. That’s it. I just installed timeshift after that and ran it like normal. No issues. Installed auto snap and grub-btrfs and I’m in the races.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.