Ok fair, but I still think that “a few bugs that make it not act like i3” is quite different from “doesn’t have backwards compat with i3 right”.

None of those bugs affect me, so I can see why my perspective of Sway being perfectly usable may differ from other users whose workflow is broken.

Looking forward to Sway having fifo, seems to work well in KDE and Gnome

So don’t use Sway, plenty of DEs are more polished.

Most of the bugs you linked to are not related to Nvidia or the post. I don’t know who is suprised thay Sway, which is relatively new, has unresolved bugs that i3, which is older, does not have.

Definitely not all of the Nvidia users, since I am one, and have no issues at all. I am even on an “unsupported” configuration, since I use Sway and they don’t officially support Nvidia.

Wayland does not suck on 60% of graphics cards. No need to spread misinformation

They are probably running a system full of “workaround” environment variables that are not needed anymore or something like that, and seeing issues because of it.

I’ve also had a flawless experience with Nvidia & Wayland recently.

For actually using the machine I would go with another Fedora Atomic distribution, such as Sway, or the XFCE or LXQt Fedora Desktops.

Appart from being a bit slow because of full fat Gnome it was very nice and usable.

Also I thought broadcasts only went to connected devices. Aka having a big subnet with 20 devices will have the same performance as a tiny subnet with 20 devices. Does the size of the subnet really make a difference, or is it only the number of actual devices?

I didn’t know there was a performance penalty to having big subnets. I’ll have to look it up and shrink them.

But this is relatively moot since all my devices talk via ipv6 now. The only thing without ipv6 support I have is Mikrotik devices that only expose their management interfaces over ipv4. Anyway these are only in one VLAN, the management one.

Ah I misspoke. I have different VLANs, not just subnets. So nothing really goes through layer 3 to talk across subnets, as nothing is allowed to go from one VLAN to another. I use them to split the networks between devices that should not talk to each other.

Then I can have fun stuff like 10.42.0.X are static IPs for known devices, and 10.42.1.X is DHCP addresses for unknown devices. This is also only one subnet, I have quite a few for management, IoT stuff, guest network, work devices.

Anyway my network is ipv6 now. Sadly fastfetch doesn’t show it, though I’d have to censor it to avoid doxxing my prefix.

Yeah I usually ran XFCE on my old laptops. But this one was wiped immediately after this. Just wanted to see full fat Fedora in action, with all the modern stuff like Wayland.

Top one is bonkers, would not recommend using it except for meme purposes.

This isn’t a donation, this is free advertising for Musk to have the police rolling around Vegas in his trucks.

Like the ships (lighthughers) in Revelation Space and other works from Alastair Reynolds :D

My grandma referred to dogs as bugs (positively) and you know what, I agree

Start avoiding Logitech then. I have had three of their Anywhere MX mice of various generations, and now an MX Master mouse. They are expensive, and have ALL had switches start failing, that I had to replace and solder. Two of my coworkers have the same mouse, and like clockwork, after one and a half years one started failing. The other one is not at this mark yet, but I bet the same will happen.

I bought a Keychron mouse to replace it. It was also cheaper.

And to clarify, my comment was not to say it was expected that mice would last that short, rather that it is possible to use it enough that it falls within the expected lifespan in clicks of the switches they give.

I mean I work 5 days a week so there is that already. That plus playing games on the evenings and weekends and I bet you can near that easily.

That’s only once every 3 seconds if you use it 8 hours per day for work.

Of course, but you said:

But the code indent is wrong, and it even changed the function definition of the unrelated next function.

It is weird to split the two in your sentence, as only the indentation of the next function definition was changed, not the definition itself.

You can just take the L and say you didn’t see that the function definition that was “added” was just “removed” at the top. It is an easy mistake to make, I know I’ve done it many times.

Actually the function definition is unchanged. The line that was “added” at the bottom was also “removed” at the top. This is just the Git diff generator being confused, which won’t come as a surprise to anyone that has ever used it.

The indendentation really is messed-up though.