I take my shitposts very seriously.

  • 7 Posts
  • 303 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle
  • As a former ADHD kid myself (as in, former kid, still ADHD), I would at least worry about how the condition might affect their academic, social, and emotional development. I was an unfortunate Gifted Kid and picked up a lot of knowledge from cartoons (back when cartoons had educational value), but that came with the cost that I never learned discipline, and never learned how to study. I know that my consistently falling test scores confused and devastated my parents.

    But all that was two decades ago. I hope that ADHD is more understood now and kids don’t have to remain undiagnosed and untreated.






  • I tried dual-booting Win10 and Arch for a few months. It was problematic.

    I had to set the clock every time I switched because one expected the hardware clock to use UTC time and the other expected local time.

    NTFS on Linux is not good. The driver works, but there are fundamental differences between NTFS and Unix-like filesystems that makes cooperation difficult (e.g. NTFS uses ACLs instead of the user/group ownership and user/group/others permissions of Unix). Windows also places additional restrictions on the filesystem (e.g. NTFS supports file names that contain :, Windows doesn’t) that can completely bork the volume if violated.

    But the worst offender, and what made me nuke Windows entirely, is Windows Update. It completely fucked up the boot partition, deleted the bootloader, then died and left Windows unusable.

    These are all issues that can be solved, if you know how to solve them. My advice is to go cold turkey and delete Windows from your life.




  • (edit) I assume you’re mounting the NTFS volume using fstab, which is how you should mount internal drives. If you’re trying to use the file manager to mount it dynamically, you really should look into how to use the fstab file.

    I’d like to see your mount options.

    As others have said, it’s best to explicitly mount it with the rw option.

    Second, because NTFS doesn’t understand the Unix-like file ownership of users and groups, you have to specify the UID and GID of the mounted filesystem using the uid= and gid= mount options. If you don’t specify these, all files within the NTFS volume will appear as being owned by root. Use the uid=1000,gid=1000 options to mount the volume as owned by your user.

    Third, use the windows_names option as well. Otherwise the filesystem will allow you to create files with illegal names, and that will completely fuck up the volume when mounted on Windows. For example, the : character is permitted by NTFS, but not by Windows.

    Although, in general, just avoid using NTFS on Linux if you can. The driver is good, but there are too many basic conceptual differences between NTFS and most Linux filesystems.










  • My setup is two screens side by side and one above. KDE Plasma 6.1 can handle it without issues, and you can make panels on any screen.

    One of the most significant drawbacks of Wayland is feature fragmentation between compositors. Unlike the X11 stack of X.Org server + window manager + compositor, Wayland compositors have to implement all of Wayland in themselves. They have to serve as the display servers, plus manage window positioning, plus render the clients, and all of that within the confines of Wayland-protocols. Building a compositor is a massive task, which is why middleware like wlroots is such a big deal. It also means that WM-agnostic tools like xrandr and xdotool are more difficult, sometimes impossible to implement.

    Consider that Wayland is still heavily under development, and that new protocols have to be implemented by every compositor separately, and that the development of wayland-protocols is an ongoing fucking trainwreck – fragmentation is inevitable, and some compositors will not have the same functionality as others (GNOME being a particularly nasty sandbag). Similarly, things that don’t work as expected in one compositor might work perfectly fine in another.

    Right now I would consider KDE Plasma to be the most feature-complete compositor that is also beginner-friendly.


  • Meanwhile you get the one thing X has: It works.

    You mean I’ve been doing everything, from work through CGI to gaming (with 120 FPS mind you) on a display that doesn’t work?

    Wayland has many issues, sure, but it’s not even close to the point where “it works” can be used to distinguish it from other display protocols. We (and by we I mean anyone willing to dedicate their life to it) could do a lot to bring X11 up to modern expectations, but it’s just not worth the effort. X11 will outlive the cockroaches, but claiming that Wayland is not a functional display protocol is incorrect and uninformed.