After a year and a half of using #FreeBSD daily, it will be impossible to go back to using #Linux unless it's minimally based on BSDs (like #Gentoo, #Arch, #NIX).
Probably start with your current distro together with #HomeManager first. That should bring you early feedback if at least the config concept is something for you.
You should think that adding a local flake.nix with a package to home-manager and install the package is trivial. I'm trying for two hours but still no progress... Sometimes #nix is frustrating.
#NixOS win: I finally figured out how to make a single network interface have a native ip while also bridging a vlan so that I can put virtual machines on a different network.
[#HomeLab#SelfHosting#Linux#Nix ]
Now that my awesome #NixOS configuration has my #ThinkPad rockin' and rollin', I figured it was high time that my #MacBookPro received the same overhaul treatment!
Was finally able to get around to setting up Nix Darwin on it, as well as reconfiguring my tiled and transparent windows and custom taskbar! God, I love how #nix can make anything even more awesome!!! 🙌🤘 :apple: :nixos:
#macbookair M2: triple boot with sonoma, #nixos and #Fedora#Asahi, I am missing the sound with nixos but cheese can use the webcam while under #fedora the sound card is ok, but not the webcam!
My boyfriend is currently learning web development (HTML and CSS right now). That motivated me to play around with #programming languages.
@array introduced me to exercism.org/ which allows me to practice languages on my local machine. Thanks for that.
I'm publishing my progress at git.daniel-siepmann.de/daniels… where you can see why #Nix is awesome. I've created a derivation for the exercism binary and one shell.nix per language.
That way I can play around with other language on my own system declarative. I guess this is a nice showcase for nix.
I've now included a separate security section, an about page, a link to the rss feed, and added a note above the auto-generated posts to explain how they were created. Please let me know if there is anything else that would be useful!
I'm looking for a more up to date distro than @system76's popos and linux mint which are both based on Ubuntu 22.04 and are now too old for #inkscape development (gtk4 issues).
I've tried Fedora and it's just not very good. I could use it just as a building OS, but having to reboot to get into a nice desktop isn't a great setup.
@doctormo
How about going with your own distro, and install #Guix (rolling release) or #Nix (new version every few months) and for development create an isolated environment with all the tools you need? I do this for fee of my projects with Guix and it is really handy and fast. (I can guide you for Guix, and give you some tips for Nix, but there are more informed folks for Nix to help you)
Question for the smarter #Nix and #NixOS people: is there an easy way to pin a package to a specific version? All I want to do is downgrade hugo from v0.124 to v0.123.8.
Right now I've got like a dozen tabs open with a bunch of convoluted answers involving overrides and custom builds. The most "straightforward" method I've seen so far is using builtins.fetchGit to reference a specific commit, but it's apparently cloning the entire nixpkgs repo, which seems excessive. Any suggestions? Thanks in advance!
I kept my twtr account for a while because brands I occasionally reach out to were still exclusively there. It’s now no longer the case so I put the account down for real :)
Since I installed Debian 2.0 (Hamm) I have only moved slightly between Debian and Ubuntu and since the discontinuation of Upstartd this is hardly hopping.
But now I'm ready to try something new...
More and more often I found myself doing things like developing my code in one terminal and running it in another with "docker -run ti -v .:/workspace xxx".
It works, it keeps my main environment clean, it is inconvenient.
The holy grail would be something that configured my environment based on my current working directory.
Over the years I've had several implementations doing that, but limited to setting bash functions and environment variables. Recently I discovered devenv.sh based on #Nix, which stopped me for a while.
But yesterday I decided to install #NixOS as my main distribution (in WSL).
Is working with multiple Lisps normal in the Lisp programmer's world? Like writing some applications in SBCL, but maybe some others in <lisp 2>, <lisp 3> etc? I would imagine the want to use the same Lisp implementation everywhere
@louis@offset___cyan Any reason why you don't use #LispWorks for the server? I've been evaluating LispWorks for the past couple of weeks, particularly because of the ability to output tree-shaken compiled self-contained builds (I had a lot of problems with save-lisp-and-die in SBCL, particularly because the GLIB version and SBCL version have to match exactly). Do you usually just recompile when you deploy to the server?
Although now that I think about it, maybe with #nix that is something that I can solve.