• 11 Posts
  • 62 Comments
Joined 9 months ago
cake
Cake day: November 8th, 2025

help-circle

  • If you’re willing to go into the terminal based editor rabbit hole, I recommend going straight to helix, coming from vim/neovim in the past it’s much easier to get into and maintain since it’s batteries included and doesn’t take huge dotfiles to configure it like you want, and the movement feels more intuitive to me than vim’s







  • iByteABit@lemmy.mlOPtoOpen Source@lemmy.mlProtonDB alternatives
    link
    fedilink
    arrow-up
    3
    arrow-down
    2
    ·
    edit-2
    2 months ago

    The data being publicized isn’t enough to call it open source, if someone decided to create a foss app that copies over new records from the ProtonDB database every night for example, you would still have a diverging dataset if you allow people to insert new records in the new app, and the ProtonDB owners could just decide to not export that data any longer whenever they want.

    That could also be true if it were open source, but I’d say it’s much more likely to happen when the main parts of it are proprietary.

    You also can’t change the data being Steam specific when the app is closed source and not accepting contributions, a foss app could become as broad or as specific as the community needs it to be.




  • I got a tower stand, the bottom of the tower had completely filled with dust and there was no airflow from there, the wheels are also very convenient for cleaning under there.

    I also cleaned the dust inside and re-applied new thermal paste, neither of which I had done for quite a while, and it already improved my temps by a lot, about 20 celsius cooler max for both the cpu and gpu.

    Here are the temps after a gaming session:










  • You’ve already done the first step, which is actually using FOSS software. That’s the only way to get real context on what you’re contributing to and find issues or lack of features that bothers you or is incredibly specific to your system or use case, and fix something that maybe would not have come up otherwise or no one would have time to get to.

    Filtering issues by ‘Good First Issue’ as someone said is also a really good way to find tasks that are relatively easy to get your feet wet with a codebase. Don’t feel bad about taking on too many of them, it’s better that someone does them all and gains enough experience to become a regular contributor, than the rest of them collecting dust until someone else like you shows up.

    Don’t worry too much about not knowing X or Y language, the great thing about being into FOSS is that you get to become a multilingual developer, which is very eye opening and educational as opposed to sticking to a language like Java and never realizing the limitations it has or even the benefits it has relative to other languages, and use that knowledge to be a better engineer overall. It’s easier to learn new languages nowadays, plenty of guides and docs to find, and AI can help for more specialized and context aware questions, just don’t fall into the trap of letting AI do the job for you, you would only be fooling yourself.

    Also don’t underestimate the value of small contributions like documentation updates, translations, creating issues, etc. You don’t need to come up with a PR for every issue you create, just finding things and keeping active is enough when you don’t have the time or energy to go the whole way.