Thanks so much to everyone who hung in this week as we’ve all worked to fix the state of the Nix community. It’s been a ride; but I think things are going to get better.
Here’s the last major piece of the puzzle — the product of several months of work from an absolutely incredible team. It’s not ready for a full announcement, but we’ve opened our beta so people who are fleeing the core Nix community have a place to go.
Btw, probably well-known by those closely involved in Nix et al, there's also #TVIX by The Virus Lounge, a #Rust reimplementation of the #Nix language. And a project that got funding from #NLnet@NGIZero
@nobodyinperson I've had the same experience recently after launching a new command line tool I created for GNOME desktops.
Having that hands-on experience with #archlinux PKGBUILDs definitely makes putting together a #nix#flake or standard derivation a lot more straightforward and easy to understand for sure! 🙌👌 :arch: :nixos:
oh yeah the secret project I've been working on for two months, @lix_project, is finally in public preview. there's a fair number of rough edges in the website and infra remaining to fix but the software is rock solid.
thanks so much to the dozens of people who have been running main daily for several weeks and reporting the few remaining issues. at this point i would say it's just a stabler, faster, more user friendly #Nix 2.18.
I think I have finally™️ (for the third or so time) found myself a solution for :python: #Python development on :nixos: #NixOS that allows me to just work with #pythonPoetry et. al. as on other distros.
The solution is to pre-build an FHSUserEnv in your configuration.nix, e.g. like this¹.
When starting Python dev work, I now execute fhs (it's fast!), or directly fhs -c 'poetry shell' and everything works as expected, including #PyPI wheels etc.
@docRekd@publicvoit Of course. It's not a general solution to be able to do Python dev on NixOS. One needs a separate nix file per project (that alone is an absolute no-go). Even if you take the time and try to make one, still no guarantee that it works (even with preferWheels=true!). Weird errors arise with nix' typical awful error messages and at this point it's not useable for general Python dev. Maybe for specific standalone Python projects you want to #nix-ify.
I like #Nix, I do not like what has happened to it.
With no explanation of what happened, the conclusion is almost certainly Internal politics.
It seems like forgejo split from gitea because it looked like gitea was going the route of gitlab. Idk if NixOS is going to commercialize though. Based on recent gossip it sounds like they’re overly adverse to commercialization. IE banning people for having DoD connections. Aux’s talk about special interest groups makes it sound like they’re going embrace that like redhat.
Today I learned: #nix-infect, to transform a vm from another distribution into #NixOS, mostly for cloud providers that don't offer this option! (Including #DigitalOcean and #hetzner). I am going to use it! :)
TIL you can use #Nix to run entire builds on a remote system, just by adding --build-host <hostname> to nixos-rebuild, as long as you have SSH access. I built a custom kernel for my Surface Pro on my server and it just worked. For all its faults and flaws, it's still a really amazing tool
New post in the #Guix packaging series! All about how inputs (libraries and utilities) that are needed to build a package are defined. Covers inputs, native-inputs and propagated-inputs. And, how to create your own package variants using modify-inputs - we slim down Weechat by 50% as a worked example 🎆
Looks like a new #nix fork is about to drop at https://aux.computer/. They're still figuring whether to migrate away from github. Hope it works out either way but freeing themselves from the grapple of Github, even if it's using folders would be better than staying there IMHO (which doesn't mean much tbf)
Every time I'm working with a #CI, I get amazed by how powerful they can get and how much they have advanced the software development realm. Tons and tons of checks and builds and etc. can be done automatically upon merging a pull request.
I wholeheartedly thank everyone how have invested the time and effort to write and maintain all these pipelines.
These said, I'm really interested to see if any active and high-profile project is using #Guix or #Nix in CI instead of these NodeJS-based ones.
I'm not really happy with the state of Nix and NixOS at the moment.
I really really like the idea to write code and generate a readonly system/program out of it.
My problem is the learning curve. There is no easy way to start. I use Nix for 4-6 months now. I still try to figure out what breaks my config or why the .. my overlay does not work.
I would love to have debugger like in python. Just show me the internal state, what are the variables, what variables even exist and what functions can be called at $line in code.
At the moment i am trying to figure out why the heck my overlay does not work ... again.
If there is a kind of debugger i would be happy with nix for now...
And i still don't get it how people can work with this software/os without getting insane if you want a custom version of a program or something not standard from cache.nixos.org .
I didn’t sign the open letter cause I’m just some guy that likes #nix & not a contributor per se. But if there are two sides and Anduril is on one of them, you can count me in with the #peacenix
Getting really sick of painstakingly migrating to some Cool New Technical Thing With Superpowers and then whoops, It's All Ethics Violations after a while.
First #Kagi - CEO is a white dude who can't read the room when a bunch of users raise serious concerns re: suicide warnings, .ru indexes, Brave collab, etc.
Now #Nix / #NixOS - BDFL is a white dude who can't read the room when a bunch of users raise serious concerns re: toxic members, shitty governance, MIC sponsorship, etc.
NixOS forked (aux.computer)
hachyderm.io/