Hacker Newsnew | past | comments | ask | show | jobs | submit | trexd's commentslogin

Declarative reproducible configuration is probably the main draw.


They stopped using Nix due to disagreements with how the project was run.

https://xeiaso.net/blog/2024/much-ado-about-nothing/


Weird article. The author is clearly heart-broken about some changes in how Nixos is managed - but what those changes were and why the author dislikes them is left completely unclear. The link to the Determinate blogpost doesn't clarify anything. I guess it might make sense to Nixos insiders...


From what I gather you fear determinate systems will guide future Nixos dev like google steers chromium or am I way off base?


What about Guix? May be more their tempo.


Nix doesn't help when the issue is a compiler bug, sadly.


This happened to me recently with verification to Coinbases's KYC system. I was repeatedly denied verification and after contacting their support on X (the only method of contacting support without logging in is social media) they gave me the same ring around that you've experienced. Ultimately I solved the issue by using my girlfriend's phone to take the pictures of my license.

The root of the issue in my case is probably caused by my camera's low quality pictures from a lack of AI post processing since I use Graphene OS. It sucks that you can no longer easily contact a human when you're really stuck.


>the only method of contacting support without logging in is social media)

But you logged in, into social media.


I bought all the parts for this last week based on the GitHub project. Looking forward to being able to use this guide!


I found that building my configuration on a virtual machine was the best way to go. This way I was not desperate to get things working and simply moved when I felt like all my essential programs were in place.


Why not just change the license to GPLv3 for the upcoming version?


The truth is that it become a race to the bottom with a lot of open source projects, specially the ones that are not hard to replicate.

If the author made the project GPL, someone else would create a similar library with a more permissive license, which would end up taking the market and making the original library irrelevant.


GPL for students and open source projects, paid license for orgs and companies. GPL itself isn't really a way to get paid for your work.


I was speaking more to preventing companies from using your open source work, but I guess in this instance the emphasis is on getting paid.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: