Features:
- Works on Nix on windows & NixOps4,
- Works on Cleanup of general ecosystems like the javascript ecosystem in nixpkgs & nixpkgs,
- Our goal to make nix mainstream,
and much more.
Link to news post: Home | DigitalBrewStudios
If you have any questions, feel free to leave them here or in our discord.
3 Likes
Are you announcing that you have the intention to work on the things mentioned?
Yes indeed. We are announcing that we’re working on things mentioned in the news post, as well as our mission to make nix a bit more mainstream.
What changed from the last couple of years you’ve been in the Nix community, did you get funded?
I have started this as my own business as a sole trader in Australia and saw the potential with nix becoming the mainstream eg. using it as a CI System. However everyone still uses GitHub actions and normal toolchains to build their app the issue with this, it’s not declarative and reproducible.
There as been works like the devenv dev environment stuff, but I want to change it so you can build apps with a simple nix bundle to build .appimages and etc.
My business is making a change to that so you have official tooling like nix bundle to bundle apps for non nix store systems and that is stable to use and production readyness for nixops4 to use in production.
Having broken/unstable toolchains doesn’t help make nix upstream.
I mean these are some pretty bold claims from someone who has 0 commits in nixpkgs and 2 commits in nix.
Sounds great and I wish you all the luck, but maybe don’t announce wishful thinking to the entire community before there’s anything to show for it?
2 Likes
There is actual work for it, It’s in drafted branches. This just announcement but our mission which we are working towards.
I would love to see some help with Flatpak Broken Issue as it’s broken.
EDIT: almost working! Requires allow broken though, due to an issue with bytestring-nums not being able to be built.