Google is spending a lot of cash to make Firefox look bad so people are unmotivated to change away from Chrome when manifest v3 is fully rolled out.

Servers, and workloads are various- DNS, ntp, databases, a few websites, internal servers running code/apis/etc for internal processes, etc.

As someone who has strong opinions on this, and not only has a job but has a job related to exactly sort of thing… We use freebsd.

Specifically to avoid shit like systemd, and other questionable choices forced down people’s throats by idiots who can’t stop touching things that work well because they didn’t invent it.

Because it’s cheaper than actually implementing working anti heat instead of just stealing control of your computer and leaving gaping vulnerabilities on it.

After all, why would they care? It’s not their computer.

Google really wants to make sure you can’t escape their ad-riddled bullshit when they get rid of Manifest v2

Removed by mod

I’d you want immutability and things that just works, snaps are the exact opposite of what he needs. I’m gearing up to swap away from Ubuntu for the same reasons as him, and the snap ecosystem is utterly fucked and accelerating my timetable daily.

I’ve never seen something so damn broken, and it gets more so every update. It’s gotten to the point of where snap store will just straight up log me out of my session out of the blue when it finds an update so it can install it, losing all of my work.

Honestly, matrix is incredibly user unfriendly. It needs to stop being held up as an option for these sort of things.

The problem here is “reasonable court.” One party in the US has spent decades stacking the courts with unreasonable judges who will agree to anything a corporation hands them.

Nah, c suite was pretty clearly in the right here. Dude left because he was pissed that a vulnerability got assigned a CVE instead of just… Not informing anyone so they could quietly fix it.

You’re not missing anything, dude just threw a hissy fit because he’s not the king of his fiefdom anymore.

The reason I care about the technical implementation shortcomings is because they don’t go away. They don’t magically fix themselves over time, they snowball, especially when the maintainers refuse to admit they’re shortcomings and insist on doubling down on them.

As time goes on, new functionality and technologies are going to emerge, and you need to be able to fold those, cleanly and reliably, into your codebase. And frankly, wayland’s devs are having trouble getting past and even current technologies implemented cleanly into their codebase, because they’re made architectural decisions that exclude those technologies. This is just going to be more and more of a problem as time goes on, imo.

• Screen recording CAN work… if client devs go out of their way to work around wayland, like OBS did. That is not a long term solution, or even a solution we should be encouraging.
• yes
• personally I have crashes on wayland, none on X11. even when x11 does crash though, you just drop to terminal. Whatever is locking your system up, it might not actually be X11 itself. Wayland, you do actually have to reboot, it’s a standing architectural issue.
• nice
• I’m on ubuntu gnome w/ AMD gpu, and they straight up do not work. You can set a global hotkey for the OS/wayland itself, but there is no way to set a global hotkey for/from a program, e.g. set a key combo for ‘clip last 30 seconds’ like I can in X11. Again, conscious design decision by wayland devs that breaks a lot of use cases. I think there’s some third party plugin for wayland that fixes this, but I shouldn’t need the wayland equivalent of nexusmods to get my window manager working. This ain’t skyrim. :P
• sleep and hibernate are pretty close to the same thing- sleep mode saves your current state to RAM, hibernate stores it to disk. hibernate uses less power draw and recovers cleanly from power loss. These days I think most front-ends call ‘hibernate’ sleep, and don’t actually provide sleep as an option, because it’s imo better. I meant hibernate, and I should have clarified, because linux does actually allow you to pick and choose.
• some appimages work, but it’s because they work around wayland. These days there’s a package you can include in your app image to hep with that iirc, but again that’s kind of dumb.
• redshift is f.lux. Basically, eye strain relief.
• toolbars, utilities, etc. For example, I have a program that adds an overlay to my screen for discord, so when someone talks in discord their avatar pops up on the left side of my primary screen. This not only doesn’t work in wayland, it can never work in wayland, because it intentionally refuses to allow programs to set their own screen position, control whether they appear over other things, or even know where on the screen they are on the screen.
• GUI applications with sudo, yes. Basically, in wayland sudo has to pipe the password arround because it doesn’t support SUDO_ASKPASS, so they work around it by piping it around with a generated shell. This vastly increases the attack surface of sudo: https://github.com/linuxhw/hw-probe-pyqt5-gui/commit/eb2d6e5145fb8571414bda57676084b7f13b94e5#diff-23cb15995f1502beebb38433bfa83204a5f45b376eaf88e2e41a0d8a1cd44722R290

Ubuntu Gnome on AMD, actually.

screen recording/sharing, automation, it’s inherant fragmentation because it decided that basic window server functionality should be implemented on the DE, basically every driver but a super small subset of drivers for devices the devs care about which do not include nvidia drivers which are a huge portion of the userbase, the absolutely ridiculous architectural choices that intentionally blocks basic functionality, and furthermore causes a crash to completely freeze your computer which forces restart, a complete failure to understand standard monitor EDID, and a refusal to allow you to set them yourself (to this day my monitor, a bog standard 144hz 1440p LG monitor, is not supported by wayland), no global hotkeys, broken sleep mode, breaks appimages entirely, no redshift, the developers made sweeping design decisions that don’t work and then get pissy and throw temper tantrums in the mailing lists when people point out that they don’t work, heavily moving away from portability and modularity (the devs think nobody uses BSD?!), windows can’t raise themselves or keep themselves raised, or absolutely position themselves, so toolbars/utilities/etc can just go fuck themselves, sudo gets broken and has to pipe passwords everywhere as a workaround which means sudo has increased attack surface on wayland, and color management is non-existent.

And this is just shit I have personally ran into the last time I tried it, which was about 4 months ago.

Something wayland lacks but Xorg has?

Basic functionality. Anyone that actually thinks Wayland is ready either doesn’t use it or is just straight coping. Maybe it’ll get there, but… honestly, probably not.

Come back to me when I don’t need to treat wayland like a bethesda game and install a bunch of mods, plugins, packages, and do a bunch of other crap just to get basic functionality.

Wow, it’s almost like that’s why they said you didn’t need a graphics card, instead of saying you didn’t need a GPU!

I keep seeing this sentiment on these posts, often with a suspicious number of up votes that don’t seem to correlate how many up votes everything else in the topic get.

Literally the only place I have EVER seen this issue was a state toll road website, which was using a timezones that didn’t actually exist but chrome added (and documented on the Internet to trick people into using it). A simple email to the website with an explanation and the correct timezones name and the problem was fixed.

Pretty sure a lot of this sentiment is either astroturfing, or people passing on astroturfing trying to be helpful.

Instead of trying to tear down things that work, try building up the distros that don’t.