Standard forgejo shoutout. It is a fork of gitea with more features following the foss philosophy. It is codeberg’s backend https://forgejo.org/2024-02-monthly-update/
Standard forgejo shoutout. It is a fork of gitea with more features following the foss philosophy. It is codeberg’s backend https://forgejo.org/2024-02-monthly-update/
You can still compile infinity from source with your own api key
I’ve gotten tired of weird regex stuff in awk, sed, and grep, so I’ve moved to perl -E for all but the most basic of things.
The main advantage of having a /home partition is that you can easily preserve it during reinstalls or during a distro hop. Reinstalls used to be more common in the past when some distros didn’t allow full distro upgrades without reinstalling. See this result which is still ranked #1 on duckduckgo
I personally use a @home btrfs subvolume which has most of the same advantages to me, and additionally allows @home and @root to share the same partition. It also allows me to use luks on everthing without bothering with lvm.
Are you sure your screen refresh rate is correct?
Zellij - a better way for a cli application to communicate with the terminal
Warp - a terminal emulater that integrates LLM completion natively
Fish - a shell that generates completions automatically from a man-page
They could be refering to the V programming language
I may be missing something, but the only machine learning focused api I know of are AMD’s ROCM, Nvidia’s CUDA, and now Intel’s oneAPI. I haven’t looked into Apple’s machine learning frameworks and I consider vulkan more of a general purpose api than a machine learning one.
Now there are 3 competing standards Edit: 6ish accually
Turing Complete Configuration
Data Based Configuration
To enable the use of flakes, you have to use the ‘extra-expiremental-features flakes’ flag.
Edit: Apparently they are called ‘extra-expiremental-features’ not ‘extra-unstable-features’. Regardless the nix docs explicitly describe them as unstable here
https://nixos.org/manual/nix/unstable/contributing/experimental-features.html
Pros
Cons
I use a shared boot partition all the time. I mount my EFI system partion on /efi. Then I bind mount /efi/$OSNAME to /boot in my fstab. Then I just manage my bootloader (typically systemd-boot or refind) manually. Any distros I install are installed in my encrypted btrfs partition within their respected subvolumes
There is also writefreely. It is fairly basic, but says it supports “publish[ing] to multiple blogs from one account”. Haven’t really used it, but it looks kinda cool imo
https://github.com/writefreely/writefreely