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).
#Gaming on #NixOS#linux is amazing! At least for launching few #steam games.
One of the game which struggled to launch or throws an error on previously distro (Endeavour OS) launches just fine on NixOS.
I love NIxOS so much! I'm going to stick with #nix for now
Abstract reads: “we show that we are able […] to rebuild 99.94% of the 14 thousand packages from a 6-year-old Nixpkgs revision.”
Section 3.2 clarifies that claim though: “We use the Nix cache [pre-built binaries] extensively in this step.” Not relying on pre-built binaries “would be a much more difficult achievement”.
Can any #nix nerds tell me how a "nix-native" program would handle configuration? If the primary way to configure my app is with a configuration.nix files, what is the best way to pass that configuration information to the app? Can the app just read the nix store directly somehow? Or would it need to write the config to a file which the app would read? Thanks in advance 😁
If an un-ergonomic API is a spike pit, then a tool wrapping it could be thought of as a partly-supported false floor above said trap:
sure, you /can/ cross safely, but a lot of the time, you step on the false tiles & then: ouch! spikes!
With the added bonus that you're now dealing with pain/complexity from the wrapper itself being in the middle of the problem/stacktrace; which could be thought of as the additional "fall damage" 🙃
oh, and because I probably have ADHD, I should clarify: the parent toot is /not/ in any way related to my /other/ ongoing thread about Matter/Thread/smart home.
It's about things like #Nix wrappers, which /sound/ like a great idea in general due to how "spiky" nix/nixlang is, but, well: see my bad analogy.
@cbleslie The goal of the #Nix board seems to be to continue ignoring the community and hope ot goes away.
Proponents of the new direction try to employ as much slippery slope, whataboutism, bad faith, strawmam, and general noise as possible to make dissent go away - with tacit board support.
Obviously neither mission can be allowed to succeed.
Spread awareness of the letter, celebrate loudly #NixOS as a first mover distro directly endorsing the western war indistry.
Okay, so I‘ve used #vim for a while and recently started using #HelixEditor not only for text editing, but also for #Java and #nix development. It‘s still not the same as using a full IDE such as #IntelliJ. But I love how snappy terminal based editing feels… so what’s next? Should I look into #emacs? Found an introduction video on YouTube that‘s just 1h 39min 😅
I like #Nix. I like #NixOS. I've been building more and more tooling in the form of #SnowfallOrg and media like #NixPkgsNews or my YouTube channel. I do not want any of my work even remotely related to murder. Ever. I am severely disappointed in the Nix Foundation's inability to reject this sponsor. This is the second time and is not an accident.
Change and guidelines must be established to prevent this from happening again.
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.