tomberek

10 ms·

1.
by tomberek 10d ago
The ability to quickly try out and verify ideas is valuable. This would have taken immensely more time to get to a stage to reasonable verify or dismiss as an idea otherwise. This saves time for builders. The author cares; this is not a pos
2.
by tomberek 1mo ago
The Nixpkgs Core team was established in Sept 2025 ( https://discourse.nixos.org/t/establishing-the-nixpkgs-core-... ), so it is a fairly new concept and idea. They've accomplished some good things as highlighted in
3.
by tomberek 3mo ago
Perhaps give boats some advantage in capacity.
4.
by tomberek 11mo ago
Presumably this would support a big improvement to both SBOM generation as well as various UX features and workflow improvements.
5.
Experimenting with Flox's new build and publish(thefridaydeploy.substack.com)
4 points by tomberek 1y ago|1 comments
6.
by tomberek 1y ago
Trading perfect reproducibility for usability: a pragmatic look at Flox's new features
7.
Docker Replacement Flox Has Libraries for Kubernetes(thenewstack.io)
5 points by tomberek 2y ago|0 comments
8.
by tomberek 2y ago
This is exactly how I can rapidly prototype things. Once proficient with this tooling is becomes very easy to quickly spin up services and PoCs. Managing it and iterating is also a breeze.
9.
by tomberek 2y ago
Random thought. Another commenter worried about the runtime of the program becoming mangled and performing destructive operations on your machine. What if you run the reducer as a source-to-source Nix derivation? Protects against dangerous
10.
by tomberek 2y ago
Agreed. Packaging is different than deployment. Devs should return to the art of packaging, such that their software can be then deployed into containers, VMs, micro VMs, whatever. That is what packaging allows, re-use. This is the sort of
11.
Get a Portable Turn-Key RAG Stack with Verba and Flox(flox.dev)
5 points by tomberek 2y ago|2 comments
12.
by tomberek 2y ago
This is excellent. Have you considered making a presentation or a write-up of the experience?
13.
Using Flox to Create Portable, Reproducible Python Environments(flox.dev)
6 points by tomberek 2y ago|0 comments
14.
Simplified Service Management with Flox(flox.dev)
10 points by tomberek 2y ago|0 comments
15.
by tomberek 2y ago
A similar article for bringing Ruby into the Nix ecosystem: https://flox.dev/blog/flox-and-ruby
16.
ML Modeling with Flaim and Hugging Face Diffusers(flox.dev)
8 points by tomberek 2y ago|0 comments
17.
Flox 1.1: Time Travel Across 100k+ Nix Packages(flox.dev)
12 points by tomberek 2y ago|0 comments
18.
by tomberek 2y ago
This is an excellent pattern. Nix uses it to allow one to create a full transitive build graph, serialized that plan, move it around, and execute it in a distributed and reproducible fashion. There are always temptations to loosen the const
19.
Run Containers Easily with Podman and Flox(flox.dev)
4 points by tomberek 2y ago|0 comments
20.
Using Jupyter Notebooks with Flox(flox.dev)
2 points by tomberek 2y ago|0 comments
21.
by tomberek 3y ago
`flox` needs Nix to function. So the rpm/dev/OSX installers first install Nix, and then installs flox itself. If you have Nix already, you can try it out as described here: https://flox.dev/docs/install-flox&#
22.
by tomberek 3y ago
That link in hub.flox.dev is wrong. The link at https://flox.dev/terms-conditions is correct. Fixing.... thanks!
23.
by tomberek 3y ago
The python ecosystem will require specific support, so at the moment we recommend using `flox` to get all of the other things that might not be managed by an existing Python package manager, and/or to install that package manager itsel
24.
by tomberek 3y ago
Yes. We have designs to allow for more powerful configuration for experts. A good example of this is let people use alternative manifest representations; JSON, Nix, etc.
25.
by tomberek 3y ago
Yes, I'm also a Nix maintainer. `nix develop` does many other things, originally based on re-creating the build environment of a derivation. This means that it is not ideal for the case of development environments that must support mor
26.
by tomberek 3y ago
Yes. For limited situations it provides a simpler interface. Flox won't provide exactly the same feature set, but there are many situations where home-manager is too much. You can consider the current `flox` environment to be similar t
27.
by tomberek 3y ago
Supporting rollback and history means disks can fill up. With Nix, this is usually due to a bunch of GC roots pointing to profiles and packages that then cannot be cleaned up. Our environments are not just symlinks, but have a declarative f
28.
by tomberek 3y ago
Nix runs alongside other distributions in various OSs, including OSX. (Windows is being looked at, do not hold your breath.) The cross-platform capability of `flox` comes from our usage of Nixpkgs, which includes allowance for some of the d
29.
by tomberek 3y ago
It's not necessarily that one is better than another; it can be complementary. I tend to think that Nix makes many of the reasons to use a container superfluous, but there still remain other reasons to use containers. For example, a ta
30.
by tomberek 3y ago
> What's your story for dropping down into 'real Nix' if required? We already have talked about this and plan to allow using Nix itself in those cases where someone needs the additional power. The current thought is to hav

More ›