ronef

6 ms·

1.
by ronef 22d ago
Loving this. Honestly I keep encouraging folks to just TRY native Nix for dev environments. So easy to set up and get value on day 1 that you'd be shocked. Also models/LLMs have made lightyear strides in the last few months to hel
2.
by ronef 1mo ago
For anyone reading this and jumping to a broader conclusion: the Nixpkgs core team disbanding does not mean Nixpkgs or Nix is dying. It does mean that this particular structure was not sustainable, very important contributors burnt out and
3.
by ronef 2mo ago
Huge plus to anyone interested in the space to check out what Graham built here! If anyone is also interested on Nix/CUDA/Capital Markets/Flox, we recently did another case study in the space - https://flox.dev&#x2
4.
Auto-Activation Is Now Native in Flox(flox.dev)
2 points by ronef 2mo ago|1 comments
5.
by ronef 2mo ago
Sharing something I'm personally excited about that's made possible with a lot of Nix/NixOS (nixpkgs) in the background by the Flox eng team. Was initially built for devX but is having a lot of pull for establishing agent inf
6.
by ronef 2mo ago
We've been working quite a bit on bringing in Nix/Nixpkg/Nixos based architecture into the space of bringing in determinism to the baseline infrastructure of our AI stacks. This also leans into the conversation around soverei
7.
AI Stack as Code: Define It Once, Run It Everywhere(flox.dev)
8 points by ronef 2mo ago|2 comments
8.
by ronef 2mo ago
Asking this with a bias since I work on Nixos.org and Flox.dev - How is the team thinking about the infra layers underneath these models? Any priority or reason to imbed determinism/reproducibility at the bottom of the stack?
9.
Mitigating Shai-Hulud Attacks with Hermetic Builds(flox.dev)
3 points by ronef 3mo ago|1 comments
10.
by ronef 3mo ago
What's the best practice right now for setting these up? We've been primarily using Nix/Flox to set up the models pretty quickly and at least with minimized amount of commands(biased Nix/Floxer) here and found it useful
11.
by ronef 3mo ago
A small note of amazement from Nix/Flox person here. Incredible to see this release and congrats! Mike, you're an allstar for so many years of contributions!
12.
by ronef 4mo ago
I.e. is this overhyped?
13.
by ronef 4mo ago
I feel we should definitely be digging way beyond the SBOM... but also wondering if the forecasting in the general ecosystem is on point or not.
14.
by ronef 5mo ago
Ron from Flox here. We recently wrote this piece on how Nix can address the emerging CVE remediation problem. We are curious to hear any feedback on our approach.
15.
Achieving CVE Remediation in an Era of Escalating Vulnerabilities with Nix(flox.dev)
3 points by ronef 5mo ago|1 comments
16.
Achieving CVE Remediation in an Era of Escalating Vulnerabilities(flox.dev)
2 points by ronef 5mo ago|0 comments
17.
Achieving Rapid CVE Remediation in an Era of Escalating Vulnerabilities(flox.dev)
2 points by ronef 5mo ago|0 comments
18.
by ronef 9mo ago
[Disclaimer: biased Flox/Nix person] There's a lot of reasons to use Nix instead of or WITH Homebrew depending on your exact needs. Where it’s paid off for me (and where I think it actually wins) is when the problem is recreating
19.
by ronef 9mo ago
Highly recommend to check this out, the blog/Arnoult does an amazing job in very succinctly breaking down the aspects of SBOMs in a Nix based infra approach. We can go way beyond the current SLSA levels and provide full provenance at t
20.
by ronef 10mo ago
And I'm back in the land of the living. Can't really beat a response from Justin Cormack!
21.
by ronef 10mo ago
Jotting down a few quick thoughts here but we can totally go deep. This is something Michael Brantley started working on a few months ago to test out how to make it super easy to ease and leverage existing Nix & Flox architecture. One
22.
by ronef 10mo ago
online community love was not in my cards going into day 3 of a newborn but I'll take it + definitely needed! thank you!
23.
by ronef 10mo ago
Yes, this hits the nail on the head. We’ve seen the same explosion in image size and rebuild complexity, especially with AI/ML workloads where Python + CUDA + random pip wheels + system libs = image bloat and massive rebuilds. With the
24.
by ronef 10mo ago
Going to sound weird but with both my hats on I super appreciate this perspective. I can only speak to some areas of Nix and Flox obviously and I know folks are looking into doing this to your point a whole lot better. Zooming in way more i
25.
by ronef 10mo ago
Ron from Flox here, woke up to feed a brand new 3 day old to see this here! On about 3 hours of sleep (over the lat 48 hours) but excited to try and answer some questions! Feel free to also drop any below <3 We did just launch this last
26.
by ronef 11mo ago
+1 to Farid, great write-up! What you’re seeing is the long-standing “deriver” mismatch: fixed-output derivations can change their .drv without changing the output path. Eelco is calling it out as well in the comment below. I believe the id
27.
by ronef 11mo ago
Bellroy is. very cool and deep in tech. We actually did a Nix in the Wild with them a while back! https://flox.dev/nixinthewild/nix-in-the-wild-bellroy/
28.
Show HN: Flox – Nvidia CUDA available for the Nix ecosystem(flox.dev)
14 points by ronef 1y ago|0 comments
29.
Flox Build and Publish(flox.dev)
6 points by ronef 1y ago|0 comments
30.
Kelsey Hightower on Nix vs. Docker: Is There a Different Way?(thenewstack.io)
4 points by ronef 1y ago|0 comments

More ›