• 0 Posts
  • 117 Comments
Joined 11 months ago
cake
Cake day: July 31st, 2023

help-circle
  • Commiunism@lemmy.wtftoMemes@lemmy.mlThis has to be a joke...
    link
    fedilink
    arrow-up
    9
    arrow-down
    1
    ·
    edit-2
    7 days ago

    I remember making a comment once on .ml about how a news source they linked isn’t too credible, with mediafactbiascheck as source for that claim (as the site had historically gotten their news wrong), and the comment got removed for “blogspamming” or something lmao

    There’s certainly a degree of powertripping going over there with the mods, and I do feel like this one is gonna be removed as well for “bigotry” against mods or something


  • Directx 11 in this case, played bg3 on Linux and that was the only option that worked, and it did work quite well.

    As for when to use one or the other, just check protondb. People usually leave what they played on, they even leave some useful launch commands or solutions to issues that could possibly arise, so it’s always worth a look.







  • My very first distro was Manjaro actually - I tried it twice but there would always be some graphics related issue I would encounter that I couldn’t troubleshoot as a beginner (even though I’d spend a week looking for a solution on forums), and I’d move back to Windows. Finally getting the courage to try out Arch which was considered the “big scary meme distro” was what made me stay with Linux.

    The biggest thing for me was that I actually knew what was installed on my system and what the function most of the major programs served (things like xorg, multilib graphics drivers, pipewire/pulseaudio, desktop environments/window managers), so whenever I encountered an issue or wanted to customize something, I would sort of know where to start looking.

    Of course, all this depends on the person - not all power users are the same. For me, arch worked best but someone else might gravitate towards fedora, debian or whatever else and their way of doing things.


  • Arch isn’t a bad choice for a new Linux user who was a power user on Windows. You get to actually know what’s installed on your system which can really help during the inevitable troubleshooting, though it’s definitely a trial by fire when it comes to manual install and setting up the environment.

    Recommending Gentoo to a new user though is a war crime.







  • It’s not the biggest issue I managed to fix, but it was definitely the hardest to figure out a fix for:

    Whenever I would boot up any game on my Linux machine I would have microstutters ever so often, and it was frequent and lengthy enough to be very annoying, and thus started my 2 month long quest to figure out what was going wrong.

    To cut a long story short, the compositor I was using had suddenly decided to do a breaking update and change the names of the backends they were using.



  • There’s pretty much only two ways you can go about it in my experience:

    1. Fail forwards and try cobbling something together, constantly using search engines to fix errors or finding libraries or getting help with those libraries. One thing you’d have to figure out is an order of operations - what do you code and in what order, which might be tough for someone new but I’d say it’s well worth it.

    2. Find some tutorial to a project and try following it (those that have step by step guide on what you should do without letting you copy paste code), then using the knowledge you gain to do the way #1 above to hopefully have an easier time figuring out the order of operations, plan out your program and what you’re gonna be coding.

    Don’t think you can avoid getting hands-on and coding something up by yourself. General coding tutorials can only get you so far and are often harmful if abused too much (aka being stuck in tutorial hell).