Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
I feel NixOS shines more on a server or specific setups. It's kind of meant for development also and occasionally you'll see some flakes or CI workflows in some project repositories. Idk I have a shell with a fhs environment and pip but it took some extra steps to get numpy, tensorflow and all C/C++ dependencies working but now I just use that for the Python stuff. And we have Distrobox, Docker/Podman... But yeah, I've invested more time in NixOS config and packaging than I'm willing to admit. Not only is it necessary to learn the functional programming language to write the declarative config... You'll also have to learn how a million of gears hook into each other to make things happen in the background. It's often not possible to do simple things without that additional (very specific) background knowledge.