Top all-time · #2428
Jetify
Company blog · jetpack.io/blogprogrammingsystems
Jetify is the company blog at jetpack.io, writing about programming and systems. Since 2022, 30 different Hacker News readers have linked it 61 times, most often “Jetpack.io Devbox – Portable, Isolated Dev Environments on Any Machine”. The last post was in 2024, but the archive is still widely read.
Too few sampled comments (22) to say how often HN recommends it.?
Why HN links it
HN readers link jetpack.io mainly for Devbox, a tool that sets up project dev environments on top of Nix, and a blog post on searching nixpkgs by package version. Comments mostly name the product rather than the writing.
Summarised by Claude from a sample of 22 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Jetify TestPilot is an AI agent that automatically creates, maintains and executes resilient end-to-end tests without human intervention.
Most-linked posts?
- Jetpack.io Devbox – Portable, Isolated Dev Environments on Any Machine9 people · 9 mentions · first linked 2023-07-10
- /devbox/8 people · 8 mentions · first linked 2022-11-19
- /devbox2 people · 5 mentions · first linked 2022-12-28
- How We Built Nix Package-Version Search for Nixhub and Devbox2 people · 3 mentions · first linked 2023-08-08
- Find and Install Nix Packages by Version with Devbox2 people · 3 mentions · first linked 2023-05-16
- Why did Nix adopt Flakes?2 people · 2 mentions · first linked 2023-06-16
- We Sped Up Nix Package Installs in Devbox2 people · 2 mentions · first linked 2024-01-12
- Nixhub: Search Historical Versions of Nix Packages2 people · 2 mentions · first linked 2023-07-17
What Hacker News says?
I think this Kelsey Hightower quote has summarized my experience working with Kubernetes: > Kubernetes is a platform for building platforms. It's a better place to start; not the endgame. https://twitter.com/kelseyhightower/status/93525292372179353... Everywhere I've worked, having developers use and develop Kubernetes directly has been really challenging -- there's a lot of extra concepts, config files, and infrast…
Comment linking /
on “Ask HN: If Kubernetes is the solution, why are there so many DevOps jobs?”Submitted Devbox: From 1000+ Container Script to less than 10 lines as a story · 10 points
HN discussionMost companies I've seen end up building some kind of framework around Kubernetes to make the developer experience tolerable. The threshold for getting started and getting a basic deployment up and running is way too high. Of course, there's a huge cost to building your own framework as well... And it's easy to get wrong. I started https://www.jetpack.io/ recently to try and build a better solution on top of Kuberne…
Comment linking /
on “Ask HN: If Kubernetes is the solution, why are there so many DevOps jobs?”Submitted Devbox Cloud Open Beta as a story · 7 points
HN discussionDefinitely a pain point I've seen in my past work as well. Even though spinning up a basic cluster has gotten easier with canned services like EKS, deploying and developing on the cluster is a major challenging for most developers without a higher level framework. My cofounders and I are working on a solution to this at https://www.jetpack.io/ . If you're interested in early access, we'd love your feedback!
Comment linking /
on “Ask HN: If Kubernetes is the solution, why are there so many DevOps jobs?”Submitted Nixhub: Search Historical Versions of Nix Packages as a story · 6 points
HN discussionHow does it compare to the existing Devbox project ( https://www.jetpack.io/devbox )? Does Flox have an optional cloud solution as well? Can Flox install specific versions of Nix packages? What about OS-specific dependencies? I've worked with tools like that for 5 years. Curious to understand what Flox brings to the table that we don't already have.
Comment linking /devbox
on “Show HN: Flox 1.0 – Open-source dev env as code with Nix”Submitted Why did Nix adopt Flakes? as a story · 6 points
HN discussionI think Devbox's killer feature is trivially searching for and installing packages by version: https://www.jetpack.io/blog/how-nixhub-searches-nixpkgs/
Comment linking /blog/how-nixhub-searches-nixpkgs/
on “Show HN: Flox 1.0 – Open-source dev env as code with Nix”Submitted Devbox: Build your Docker image from `scratch` as a story · 6 points
HN discussionor https://www.jetpack.io/devbox/ :ˆ)
Comment linking /devbox/
on “Show HN: Flox 1.0 – Open-source dev env as code with Nix”Submitted Devbox 0.0.5: Node and PHP Support, Init Hooks, and More as a story · 5 points
HN discussionSeems like Nix is having a bit of a moment. After devbox[1] was released I started looking into Nix, and there's a lot happening. I'm staying away from these Nix wrappers and learning how to do some basic nix-shell work, myself. Until it's proven the wrappers are adding real value, not just trying to hide scary scary Nix from devs who only feel safe in YAML files. For the curious, this post[2] describes mixing Nix a…
Comment linking /devbox/
on “Devenv.sh: Fast and reproducible developer environments using Nix”Submitted Devbox Cloud – Low latency development environments powered by Nix as a story · 4 points
HN discussionLearning the syntax is the easy part, the language is quite simple with few rules. But, I agree with the other sentiments. It needs a better UX for it to be mainstream. There are few attempts being made[1][2], only time will tell 1: https://www.jetpack.io/devbox/docs/ 2: https://devenv.sh/
Comment linking /devbox/docs/
on “Tea: A new package manager from the creator of brew”Submitted We Sped Up Nix Package Installs in Devbox as a story · 3 points
HN discussionWe switched to using Nix at our startup because the rebuild time, reproducibility, and performance of Docker (especially on MacOS) were really slowing us down. Building and starting our dev container could take several minutes if we busted Docker's layer cache, but with Nix we never had to worry about that. We open sourced our Nix dev environment tool (Devbox), and wrote a bit about why we switched here: https://www…
Comment linking /blog/devbox-turn-a-1000-container-script-into-10-lines/
on “NixOS: Declarative Builds and Deployments”Submitted Breaking Through VSCode Env Restrictions with Devbox and Nix as a story · 3 points
HN discussionIf you don't want to fully commit to the OS or the Package Manager, you can use Nixpkgs alongside your OS and other package managers by installing Nixpkgs on your Mac or Linux OS. For the functional language and UX, I agree there's room for improvement. If you don't want to dive into learning Nix, you could use a wrapper that simplifies the UX for creating projects. We built one called Devbox ( https://jetpack.io/de…
Comment linking /devbox
on “NixOS: Declarative Builds and Deployments”Submitted Devbox 0.2.0: Automatic Nix Installer, Plugins, and Background Services as a story · 3 points
HN discussionYou should check out Devbox ( https://jetpack.io/devbox ) if you want local dev without the container overhead. It provide a nice interface for creating native, local dev environments using the Nix package manager, which is especially helpful if you or your friends struggle with the Nix language. It also lets you use your local tools with your dev environment.
Comment linking /devbox
on “Ask HN: How can I make local dev with containers hurt less?”Submitted Do Repeat Yourself: Global Packages Considered Harmful as a story · 3 points
HN discussionHave you considered integrating this functionality with this nix project builder? https://bob.build/ Or this dependency installer that uses nix? https://www.jetpack.io/blog/devbox/ It is amazing to see all this user-friendly tooling come out now that is leveraging nix.
Comment linking /blog/devbox/
on “Riff, automatically provide external dependencies for Rust projects”Submitted How We Sped Up Nix Package Installs in Devbox as a story · 2 points
HN discussionI think the split between Flakeful and Flakeless Nix that the article mentions is a big challenge for developers coming in new to the ecosystem. There's a video that recently circulated of Geohotz trying Nix from scratch[0], where the mixed messaging on whether to use Flakes caused a lot of initial confusion. We've gone pretty all in on Flakes with our Devbox product[1] -- We think they simplify a lot of confusion o…
Comment linking /blog/why-did-nix-adopt-flakes/
on “Flakes aren't real and cannot hurt you: using Nix flakes the non-flake way”Submitted Jetpack.io Devbox – Portable, Isolated Dev Environments on Any Machine as a story · 2 points
HN discussionPersonally, I think because its feature-set is currently very much "scattered". Nix is in the transition to use 'flakes': a new concept that gives a bit more structure and allows easier reuse of Nix packages, NixOS modules and more. In addition it includes a standardized 'lock' file. Lock files are quite useful (or even essential) for reproducibility. However, it is in experimental phase for more than 4 years now. I…
Comment linking /devbox/
on “Zero to Nix, an unofficial, opinionated, gentle introduction to Nix”Submitted Nixhub: Search Historical Versions of Nix Packages as a story · 2 points
HN discussionThank you all for the informative advices. Here is the summary for those who are in the same situation: 1. Run Windows on Linux by using VM for the applications you can’t run on Linux Risks: * some softwares may attempt to detect VMs and refuse running * Anything what needs to touch hardware may not work. 2. separate "data" partition on D: 3. back up %APPDATA% and %USERPROFILE% 4. learn chocolatey, scoop or winget W…
Comment linking /devbox
on “Ask HN: Cleanest way to manage Windows OS?”Submitted Find and Install Nix Packages by Version with Devbox as a story · 2 points
HN discussion
