• 0 Posts
  • 41 Comments
Joined 2 years ago
cake
Cake day: July 5th, 2023

help-circle




  • it’s great if your commits are smaller and more focused. main issue is it can be harder to solve some diff issues as it requires solving merges at each commit being rebased. so if you have a large feature branch that can be challenging when it starts to diverge a lot (ex: bug fixes on main). though the argument then is more for keeping branches smaller and focused which is a better process imo.

    just beware it can be confusing for newer git users and when using shared branches can cause no ff commits.





  • the 1000x before bit has quite a few sideffects to it as well.

    • lesser used languages suffer because there’s not enough training data. this gets annoying quickly when it overrides your static tools and suggests nonsense.
    • larger training sets contain more vulnerabilities as most code is pretty terrible and may just be snippets that someone used once and threw away. owasp has a top 10 for a reason. take input validation for example, if I’m working on parsing a string there’s usually context such as is this trusted data or untrusted? if i don’t have that mental model where I’m thinking about the data i might see generated code and think it looks correct but in reality its extremely nefarious.



  • https://wiki.archlinux.org/title/Gamescope

    might go through some of those troubleshooting steps and make sure you have drm kernel modeset.

    one other thing you might try (at end of the page) by setting LD_PRELOAD=”” with the command which can at least rule out features that sometimes break on certain games. I’ve had game recording and overlay cause similar issues and could only launch after disabling those in game settings.

    also might not need gamescope? mesa 25.1+ and proton 10+ have a lot of the features built in and I’ve not noticed much if any performance difference. now i only use gamescope if i run into issues and usually only if protondb shows consensus that you need to use gamescope or specific workarounds.








  • caches are never really a concern to me they will regen after the fact, from your description i would worry more about db, this is dependent though in what you’re using and what you are storing. if the concern is having the same system intact then my primary concern would be backing up any config file you have. in cases of failure you mainly want to protect against data loss, if it takes time to regenerate cache/db that’s time well spent for simplicity of actively maintaining your system