tomberek

10 ms·

61.
by tomberek 4y ago
I’m looking to put one together in Bay Area for next week or so. DM me if interested or if you know more people in the area.
62.
by tomberek 4y ago
There are two sides to this problem, the first is to improve the UX, but the second is to clearly describe a compelling reason for people to adopt. It is very tempting to only blame the first, but I think we need to also need to tell a bett
63.
by tomberek 4y ago
Be able to start with a broad understanding and be able to dig into specifics for your area of expertise. Be able to explain the connection between the larger scope and the details. Take a look at the values ( https://www.usds.gov
64.
by tomberek 4y ago
This usage is very similar to how people sometimes use (or abuse) Makefiles to create run-scripts. Nix's special gift is that you can talk about external resources - such as packages - and safely bring them into existence.
65.
by tomberek 4y ago
I'm reading these. It seems this is where a better description of what NixOS (and it's module system) is. My suspicion is that by starting with NixOS it is harder to be introduced to the simpler concepts. It is best to think of th
66.
by tomberek 4y ago
1) what would you consider to be "wow" or magic that would go beyond a+b. What is steps c+d that would be incredible value? 2) We're working on stabilization... just asking for a bit of patience.
67.
by tomberek 4y ago
I am working on the Nix project; resolving this "in-between stage" is our highest priority at the moment. I'd like to better understand two independent things: 1. What were the drivers and motivators for you to try Nix? What
68.
by tomberek 4y ago
Best seems to be when you can transition between various representations smoothly and intuitively; between iterative development, isolated builds, containers, deployment and so on. The design difficulty is how to craft a good user experienc
69.
by tomberek 4y ago
It would be helpful to teach people without so much being done by mkDerivation or other builders. While they provide value, they sometimes block learning. I like start with super simple example, if possible.
70.
by tomberek 4y ago
As we make flakes stable, this will improve as the docs can prioritize this information, and tooling can focus on making this more clear. On a much longer horizon, future Nix language (eg: Nickel) improvements provide a gradual typing syste
71.
by tomberek 4y ago
We've seen the opposite. New package managers are built with a much better understanding of the problem space because of Nix and sometimes explicitly taking ideas and concepts. This results in those new systems being far more compatibl
72.
by tomberek 4y ago
My main mission is to make Nix and Nix-based technology mainstream. Please reach out if you are interested, have thoughts or ideas. (plus we're hiring: https://floxdev.com/careers ) This involves improving Nix itself,
73.
by tomberek 4y ago
Can you clarify what parts you don't like. I think it's important to distinguish so I know what portions to work on (and figure out how to fix it). Is it: the language syntax itself, the idioms used in Nixpkgs, the module system,
74.
by tomberek 4y ago
I work for Flox and maintain Nix. AMA I'm excited to see more interest in the core ideas this technology brings. Our vision is to make it accessible - bring this set of super-powers to the world.
75.
by tomberek 4y ago
Nix is a package manager. But it can weave together multiple package managers so it frees you from being locked in to any one particular language, OS, architecture. The proof of this that we also ended up making a full OS (NixOS). Then ther
76.
by tomberek 4y ago
I'm working on this project and constantly trying to find the right feature set to make Nix-based technology easier to adopt. We are still early in design and implementation so feedback for either `flox` or `nix` is valuable. AMA
77.
by tomberek 4y ago
Handling all cases of pre-existing Nix installations, (multi-user, single-user, incomplete, broken, etc) is something we are trying to improve. There is also upstream community work going into improving this experience and we will adopt th
78.
by tomberek 4y ago
I tried once before on Mac, but never could get it working properly. What do you think about our native OSX installer?
79.
by tomberek 4y ago
Very good question. How will we make money? What is our monetization strategy? We have nothing to hide here. Our monetization is focused on increasing corporate and organizational use. 1. We love Nix and what we can do with it. 2. We
80.
by tomberek 4y ago
hypothetical Dockerfile: FROM python FROM nodejs RUN sh -c 'python ... | node ...' Imagine this Dockerfile being valid. We want to express the idea of composing these two images into one and using binaries from bo
81.
by tomberek 4y ago
We think the ability to hopscotch between projects and ecosystems without fear is a key value proposition of Nix-based technologies. Our approach is to address the entire user experience from installation and docs all the way to developing,
82.
by tomberek 4y ago
We see a few tools that do a similar built-on-top-of-Nix approach, so we released a Rust library that makes using the "command line API" in a more type-safe manner: https://github.com/flox/runix
83.
by tomberek 4y ago
> This sounds in some ways pretty similar to something I'd been imagining for Nix, particularly for the purpose of grabbing package definition sources which have been known to work for a given version or range. (The use case is auto
84.
by tomberek 4y ago
(i'm on the flox team): A major point of feedback we got from non-Nix users were that they wanted something similar to other package managers. So we looked at the primary differences and focused on designing a user experience with few
85.
by tomberek 4y ago
Hi HN! From the flox team; today we’re thrilled to release the flox CLI beta to the public as an open-source project, to give developers seamless access to the powers of Nix. Try it now via the flox CLI ( https://floxdev.com/
86.
by tomberek 4y ago
winning
87.
by tomberek 4y ago
Pretty sure I started with this: https://github.com/prest/prest/blob/main/cmd/root.go And from there you can execute your own command and add handlers or other things as you wish.
88.
by tomberek 4y ago
I’ve used Prest (the Go reimplementation of PostgREST) because I could more easily customize or bring it in as a library in a larger application.
89.
by tomberek 4y ago
Yes! I did two years in awk ( https://github.com/tomberek/advent ) and loved the ability to dig in and truly grok the language. The performance wasn’t bad, but the multidimensional array support and ergonomics were…meh.
90.
by tomberek 4y ago
We are doing heavy re-factoring and re-design, so there isn’t much useful to see at this point. We are looking to refine the design and user experience. We do plan to have all the client portions open-source once we have less churn. Most of

More ›