• 0 Posts
  • 28 Comments
Joined 4 years ago
cake
Cake day: February 18th, 2021

help-circle






  • nix/guix can be used on any distro and it provides a way to organize .config files so that if the .config directory gets deleted or accidentally modified for some reason, restoring it would be very easy. By putting the configuration in a git repo, it also makes it easy to restore previous configurations. I accidentally deleted a bunch of stuff in my .config directory once and that’s one of the reason I use this tooling now, so I thought OP would find it helpful also







  • I use git primarily via cli also, the text editor integration (with helix) highlights information such as what lines haven’t been committed and makes it easier to access other files in the repo, the fish integration tells me if there’s files that haven’t been committed or commits that haven’t been pushed without having to run git status


  • As much as I hate GitHub, for in-person projects involving multiple people I usually end up having no choice since they usually think GitHub is the most important programming tool ever and nothing I do is going to convince them to create an account on something that’s not GitHub.

    For personal stuff I use Forgejo and disable everything except the code view, so I have a quick way to show people stuff I’m doing (for career reasons).

    If I was doing a project with multiple people and actually got to chose the platform I would probably use Forgejo or Codeberg and make use of the project management features.

    Pijul looks interesting but the ecosystem is very lacking and it doesn’t integrate well with Guix which I base a lot of my workflows around, so until this improves switching to pijul creates more problems than it fixes. The only other VCS and frontend I’m familiar with is GitLab which I don’t use anymore self-hosted since Forgejo is more performant and the main version randomly deleted all my repos and changed all sorts of stuff.

    cgit also looks interesting, I might look into it.



  • I own an M1 Air running Asahi Linux because I heard very good things about the laptop when I got it and it was a reasonable price. I don’t have a Framework to test alongside it so I don’t know how it compares with the latest x86 chips. The M1 touchpad is awesome, aesthetics are great with it being light and the material being a lot more durable than my HP Envy laptop that kept getting random dents, doesn’t have the hinge misalignment issue, screen is also good. Battery life and performance is great on macOS, not as impressive on Linux (performance is still good aside from missing hardware processing support for certain things, I do end up bottlenecking it when compiling Rust programs), lack of fan noise is nice but also bad for cooling, with Linux it tends to get warm and throttle. Asahi Linux is very impressive but still missing microphone support and doesn’t support FDE which is extremely precarious, harder to use alternative distros to Fedora Workstation. Repairability is shit, the keyboard is also shit.

    The newer M* models don’t have good Asahi Linux support and look overpriced and I don’t even know if the Air line still offers 16GB RAM models which is a must have (32GB is better). At this point in time if my Macbook were to randomly die my next laptop probably won’t be a Macbook (unless I replace it with another used M1), also I wouldn’t recommend it to most people right now because of issues with Asahi Linux being under development like the two I pointed out earlier.



  • A lot of people say it’s good although personally it hasn’t been a huge improvement for me, I’m guessing there’s certain hardware-software integration in macOS and software optimizations that contributes to the battery life that isn’t happening in Linux. It’s dying less quickly than my HP laptop though. I also tend to not close stuff so that may be a problem.