“How am I going to be racist today? OOH, the parallel command is pretty woke”
potatoguy
- 1 Post
- 10 Comments
All these “concerned” comments about systemd, wayland, etc, always seemed dog whistling to me. I have critiques about these projects, but the specific things this specific type of people says always comes coded in some form of racism/transphobic/mysoginistic rethoric. Just changed from gamergate to linuxgate.
So i’m not surprised that they turned mask off like this.
Look at any anti-systemd channel, the comments are always the worst thing ever. Some lkml reading channels have these comments too.
potatoguy@potato-guy.spaceto Linux@programming.dev•The Latest X.Org Server Activity Are A Lot Of Code Reverts4·11 days agoYeah, I think a fork fits that purpose too.
About Lunduke 2.0, Idk, but i feel a mixture of distrotube (like the gun video) + luke smith + a lot of people from that era maybe.
potatoguy@potato-guy.spaceto Linux@programming.dev•The Latest X.Org Server Activity Are A Lot Of Code Reverts14·11 days agoYeah, I see that the fight is a bit ambiguous, CoC, etc, but even linus himself got to him in 2021 because of mRNA vaccines. His work was important, but breaking things in a project that’s so old, and with so many things depending on it (like my old computer), and turning into Lunduke 3.0 seems very bad.
This happened in a release version and in the git version too, I tried the git version after seeing the problem in the release version.
Edit: Idk, but this blunder might have make xorg deprecated a lot faster than even before this.
potatoguy@potato-guy.spaceto Linux@programming.dev•The Latest X.Org Server Activity Are A Lot Of Code Reverts31·11 days ago“There was also a revert to avoid unnecessarily breaking the NVIDIA driver. It was also commented by NVIDIA that some additional requests for other reverts are coming too.”
Did this dude break resume/suspend on nvidia in x11? I think last year x11 on nvidia just stopped suspending at some time (I was trying some things on x11) and in wayland it worked, I even moved to xorg-git, but the errors persisted. If this is related, dude was/is the worst developer ever.
potatoguy@potato-guy.spaceto Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com•You have been blocked from The New York Times because we suspect that you're a robot.English17·11 days agoIt just moved to gitflic and now requires a manual install on their .xpi file.
I deleted a post because it was the dumbest shit ever written by humanity. I was drunk at the time…
potatoguy@potato-guy.spaceto 196@lemmy.blahaj.zone•For those who as kids also wondered what would happen if you cut out "SIM card" from bank card, this stupid rulepost is for youEnglish31·13 days agoThese cards have different informations inside of it, so checking for credit card number + the secret number is different than the cell phone number + carrier information, etc, so it gives mumbo jumbo to the reader if it’s not the same type, but people already know that. Sorry for commenting irrelevant information.
But good to know that a credit card can’t just have a random cell phone information hahaha.
potatoguy@potato-guy.spaceto Linux@lemmy.ml•Wasted weekends trying to make touchscreen work5·18 days agoWhat is the cpu? If something, zswap (250mb) with lz4 and zram (2gb on disk) with lz4 too, on a lightweight distro on btrfs with lzo compression might make it usable. Disk compression might make it usable on the disk side and memory compression might make it run at least not extremely bad on the cpu side. Maybe cachyos with gnome (i know, but it is the only DE with good touchscreen) can be at least usable.
If more things, I can try to help. I have a linux tablet.
Edit: Maybe more space (external sd card with btrfs and lzo) could be used as /home too, but only with more information given, what is the setup?
Edit: My config that I made it work and run decently:
I think Wine has had WOW support for some time and it seems it will be the default at some time (arch moving to wow64).
Edit: What is WOW64
WoW64
All transitions from Windows to Unix code go through the NT syscall interface. This is a major milestone that marks the completion of the multi-year re-architecturing work to convert modules to PE format and introduce a proper boundary between the Windows and Unix worlds.
All modules that call a Unix library contain WoW64 thunks to enable calling the 64-bit Unix library from 32-bit PE code. This means that it is possible to run 32-bit Windows applications on a purely 64-bit Unix installation. This is called the new WoW64 mode, as opposed to the old WoW64 mode where 32-bit applications run inside a 32-bit Unix process.
The new WoW64 mode is not yet enabled by default. It can be enabled by passing the --enable-archs=i386,x86_64 option to configure. This is expected to work for most applications, but there are still some limitations, in particular:
Lack of support for 16-bit code. Reduced OpenGL performance and lack of ARB_buffer_storage extension support.
The new WoW64 mode finally allows 32-bit applications to run on recent macOS versions that removed support for 32-bit Unix processes.