Hacker Newsnew | past | comments | ask | show | jobs | submit | edu4rdshl's commentslogin

It's fun how most of the complaints are like "it works fine on Gnome but I will still blame Wayland because my tiling WM doesn't support it". So maybe try using a proper Wayland implementation

The Chrome crashes when resizing a window doesn't makes any sense, apart from being a WM fault. The Xwayland scaling, again, has native scaling support on Gnome. Same for the monitor resolution problem (which he acknowledged). Same for font rendering. Idk.


GNOME’s “proper wayland implementation” also does not work with my monitor, as I explained in the article:

> By the way, when I mentioned that GNOME successfully configures the native resolution, that doesn’t mean the monitor is usable with GNOME! While GNOME supports tiled displays, the updates of individual tiles are not synchronized, so you see heavy tearing in the middle of the screen, much worse than anything I have ever observed under X11. GNOME/mutter merge request !4822 should hopefully address this.


> And Google helped it happen No, it doesn't, you were just stupid. That field has always been modifiable.

Every action you did is what you hear multiple times every week about people falling in pishing, and you continued.

Finally, it was just some crypto shit so not a big deal.


It's... weird, and even absurd at some point.


You can continue using `docker-compose` (the provider) with `podman compose`. It's the default provider if installed.


A small article that will reply most questions that arise when migrating from Docker to Podman.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: