That’s what the paper was about, the law also applies the in reverse, adding the space protects the user because it makes it harder to click on the hitbox.

But something that’s different would rationally be called not copying, whereas you categorize it as poor copying. Interesting.

I would categorize it as poor copying because the copy doesn’t conform to the design / UX patterns that were present on the “original” work.

My point is: if you want to copy / be inspired by others at least do it right.

+1 for this. This is kinda the same issue with encoding, just UTF-8 everything and move on.

Here’s the problem, RCS isn’t a truly open thing and Google kind of maintains a lot of the software that even carriers use for it. It essentially opens the door for the tech companies to take over yet another big chunk of the carrier services and tap into more user’s data at the network level.

In June 2019, Google announced that it would begin to deploy RCS on an opt-in basis via the Messages app, with service compliant with the Universal Profile and hosted by Google rather than the user’s carrier, if the carrier does not provide RCS

In October 2019, the four major U.S. carriers announced an agreement to form the Cross-Carrier Messaging Initiative (CCMI) to jointly implement RCS using a newly developed app. This service was to be compatible with the Universal Profile.[33] However, this carrier-made app never came to fruition. By 2021, both T-Mobile and AT&T signed deals with Google to adopt Google’s Messages app.[34][35][36] In 2023, T-Mobile and AT&T agreed to use Google Jibe to implement RCS services, and in 2024 Verizon agreed to use Google Jibe.

Apple stated it will not support Google’s end-to-end encryption extension over RCS, but would work with GSMA to create an RCS encryption standard.

it is trivial to disable all animations

Yeah you can go into settings and toggle of a switch, however they don’t disable everything. ~

Whenever you go into Settings > Accessibility > Enable Animations and disable it one would expect that ALL animations would be disabled while in fact they aren’t. It should behave like Xfce that is, click on something and get the instant result, no delay, no very small animation / fade like GNOME still does.

Bottom line: that option in GNOME is misleading and doesn’t do what it advertises.

To be honest I felt a bit lost on MacOs Catalina and felt like everything was difficult compared to Gnome.

Just because you aren’t used to the macOS workflow it doesn’t mean it is bad - that’s the same argument you GNOME fan boys do with Windows users ;)

But I guess Gnome is taking a lot of inspiration from the MacOs aesthetic, and it’s okay with me because it looks great.

Yes, it’s okay, and that was never an issue in this discussion. The issue is that they didn’t took enough inspiration on basic UX patterns.

Yes ksmtuned is your friend. For VMs it can be managed / enabled like any other Linux Kernel + QEMU/KVM running with KSM enabled.

On LXC containers it may be a bit harder as it depends a LOT, best results if you’re using systemd both the host and containers. It may work out all out of the box or you’ll have to resort to ksm_wrapper in both the Incus executable and the stuff running inside your containers.

Don’t forget that:

KSM only operates on those areas of address space which an application has advised to be likely candidates for merging, by using the madvise(2) system call: int madvise(addr, length, MADV_MERGEABLE). https://www.kernel.org/doc/Documentation/vm/ksm.txt

How does it handle Windows VMs

As one would except from QEMU… https://blog.simos.info/how-to-run-a-windows-virtual-machine-on-incus-on-linux/

Does the WebUI give a nice and easy novnc window

Yes it works fine. https://youtu.be/wqEH_d8LC1k?feature=shared&t=508

Actually it would be interesting to see cockpit-machines move to Incus as a virtualization backend and support both LXC containers and QEMU VMs tat way.

This is an application of Fitts’s law. I saw some paper referencing it to back that kind of margins on destructive actions but I don’t remember the title.

Your point being…?

Apple thinks their users are smart enough to use tags, while Gnome developers think the user are too dump to use tags

Isn’t this ironic? The DE with a user base that is way more tech savvy people thinks users can’t use tags.

macOS has no proper software management, all apps try to up-sell me on their shitty i-cloud offerings,

What are you talking about?? At least on macOS app icons are consistent not the crap they are on GNOME.

macOS (…) setup cannot be properly automated

This couldn’t be further from the truth. Apple makes automated setup even easier than it is on MS ecosystems, companies can literally buy a computer on the Apple Store and have it shipped to an employee with the companie’s profile pre-installed by Apple without even needing to touch or open the box. The employee get’s the computer, opens the box and just has to login with this corporate account.

You’ve Apple’s own MDM, Jamf, JumpCloud and so many others. Even Ansible can be used to configure, setup and automated macOS deployments.

macOS feels too slow for the hardware it runs on…

Well at least it doesn’t like a 5 second pointless fade animation after every single click like GNOME does, nor does it bundle web technologies for theming that make the DE be as slow as it can get when it comes to rendering a new window.

You aren’t wrong, but that has nothing to do with he issue at hand. They should copy each other if a solution is good, and that’s the issue here, GNOME forgot to copy a good UX practice that Apple actually took the time to implement.

According to the UX experts you don’t need the space between the save and discard buttons as long as the “save” is the first one. Missclick are more prone to happen from top to bottom than the other way around, so if the user wanted to hit “save” it’s more likely he will click above the button than it is to click “discard”. Same logic applied down there, when the using is looking to cancel it’s easier to missclick and hit the “discard” button than anything else.

I’m curious what you are referring to losing work due to a misclick?

If you place “Discard” and “Cancel” next to each other, without a margin in between, is easier a user looking to click on “Cancel” to click on “Discard” and lose a document. This is more common than people think and that’s why Apple added the margin there and also why any good UX manual tells you to add a margin for destructive operations like that one.

LXC is worse than virtualization as it pins to a single core instead of getting scheduled by the kernel scheduler. It also is quiet slow and dated. Either run Podman, Docker or full VMs.

First what you’re saying about the scheduler isn’t even what happens by default, that was some crap that Proxmox pulled when they migrated from OpenVZ to LXC. To be fair, they had a bunch of more or less valid reasons to force that configuration, but again it due to kernel related issues that were affecting Proxmox more than regular Ubuntu and those issues were solved around the end of 2021.

Now Docker and LXC serve different purposes and they aren’t a replacement for each other. Docker is a stateless application container solution while LXC is a full persistent container aimed at running full operating systems…

Docker and LXC share a bunch of underlaying technologies at on the beginning Docker even used LXC as their backed, they later moved to their execution environment called libcontainer because they weren’t using all the featured that LXC provided and wanted more control over the implementation.

For those who really need full systems is LXC definitely faster than a VM. Your argument assumes everything can and should be done inside Docker/Podman when that’s very far from the reality. The Docker guys have written a very good article showcasing the differences and optimal use cases for both.

Here two quotes for you:

LXC is especially beneficial for users who need granular control over their environments and applications that require near-native performance. As an open source project, LXC continues to evolve, shaped by a community of developers committed to enhancing its capabilities and integration with the Linux kernel. LXC remains a powerful tool for developers looking for efficient, scalable, and secure containerization solutions. Efficient access to hardware resources (…) Virtual Desktop Infrastructure (VDI) (…) Close to native performance, suitable for intensive computational tasks.

Docker excels in environments where deployment speed and configuration simplicity are paramount, making it an ideal choice for modern software development. Streamlined deployment (…) Microservices architecture (…) CI/CD pipelines.

Anyways…

It also ships with a newer kernel than Debian although it shouldn’t matter as you are using it for virtualization.

It matters, trust me. Once you start requiring modules it will suddenly matter. Either way even if they ship a kernel that is newer than Debian it is so fucked at that point that you’ll be better with whatever Debian provides out of the box.

Check the bottom of reply, there’s a link there with my experience over the years.

Typically I just run binaries of the services I use, and I don’t tend to use docker or other things

That’s essentially what I do in my NAS with LXD, it’s a great use case for it.

Enjoy.

You can put Incus on a lot of different systems. Don’t like systemd? Put it on Void. Want a declarative setup? NixOS. Minimalist? Alpine.

This is great, yeah.

I’ve always thought Bootstrap, the web design library, has a good set of base colors

Yes it does. Those guys did a really good job.