Show HN: Flox – Nvidia CUDA available for the Nix ecosystem
Show HN (score: 9)Description
As of today, NVIDIA officially recognizes Canonical, SUSE, CIQ, and Nix—via Flox—as supported distributors for CUDA. Full blog - https://developer.nvidia.com/blog/developers-can-now-get-cud...
This is a huge win for the Nix community. For years, CUDA on Nix was possible but painful—builds could take hours, and redistributing prebuilt binaries was blocked by NVIDIA's licensing requirements.
NVIDIA's growing engagement with key Linux distributions reflects the company's evolution in working with open source communities. Now, for the first time, NVIDIA is allowing these vendors to package and serve the CUDA Toolkit and CUDA-accelerated packages directly from their package repositories.
That means Ubuntu users can get CUDA via `apt`, SUSE users via `zypper`, Rocky Linux users via `dnf`, and Nix users simply by declaring CUDA dependencies in their Nix expressions, `shell.nix` files, or flakes. Across all four platforms, developers can now pull in prebuilt, prepatched CUDA software—including huge packages like PyTorch, TensorFlow, TensorRT, OpenCV, ffmpeg, and more.
On Nix (my own bias showing), setup is straightforward: just add Flox's cache as an `extra-substituter` in your `nix.conf` or `configuration.nix`.
More from Show
Show HN: HTTP:COLON – A quick HTTP header/directive inspector and reference
Show HN: HTTP:COLON – A quick HTTP header/directive inspector and reference Hi HN -- I built HTTP:COLON, a small, open-source web tool for quickly checking a site’s HTTP response headers and learning what they mean as you go.<p>Link: <a href="https://httpcolon.dev/" rel="nofollow">https://httpcolon.dev/</a><p>What it does<p>- Enter a URL and fetch its response headers<p>- Groups common headers into handy buckets (cache, content, security)<p>- Includes short docs/tooltips for headers and directives so you can look things up while debugging. I find hovering on highlighted headers quite useful!<p>Supports different HTTP methods (GET/POST/PUT/DELETE)<p>Deep links<p>- You can link directly to a host, e.g. <a href="https://httpcolon.dev/www.google.com" rel="nofollow">https://httpcolon.dev/www.google.com</a><p>(or any domain) to jump straight into inspecting it.<p>Why I made it<p>- I kept bouncing between DevTools, MDN, and random blog posts while debugging caching + security headers. I wanted one place that’s quick for “what am I getting back?” and “what does this header/directive do?”<p>It’s in beta, and I’d love feedback on:<p>- Missing features you’d want for day-to-day debugging (export/share formats, comparisons, presets, etc.)<p>Thanks!
Show HN: I made R/place for LLMs
Show HN: I made R/place for LLMs I built AI Place, a vLLM-controlled pixel canvas inspired by r/place. Instead of users placing pixels, an LLM paints the grid continuously and you can watch it evolve live.<p>The theme rotates daily. Currently, the canvas is scored using CLIP ViT-B/32 against a prompt (e.g., Pixelart of ${theme}). The highest-scoring snapshot is saved to the archive at the end of each day.<p>The agents work in a simple loop:<p>Input: Theme + image of current canvas<p>Output: Python code to update specific pixel coordinates + One word description<p>Tech: Next.js, SSE realtime updates, NVIDIA NIM (Mistral Large 3/GPT-OSS/Llama 4 Maverick) for the painting decisions<p>Would love feedback! (or ideas for prompts/behaviors to try)
Show HN: Hurry – Fast Rust build caching
Show HN: Hurry – Fast Rust build caching Hey HN, we’re Eliza and Xin. We’re working on Hurry, an open source drop-in tool that adds distributed build caching to Cargo with (almost) zero configuration. Wherever you run cargo build, you can run hurry cargo build instead, and expect around 2-5x (our best benchmark is 22x) faster builds.<p>We built this because we were dissatisfied with the current build caching options available for Rust. Buck and Bazel require learning a new tool. GitHub Actions and swatinem are too coarse-grained (either the whole cache hits, or none of it does) and finicky to debug, and cargo-chef and Docker layer caching have the same problems.<p>We wanted something that could restore cache at the package level, did not require integration-specific setup, and worked everywhere.<p>Hurry is fully open source under Apache 2. You can try it out now with our cloud hosted caching service at <a href="https://hurry.build" rel="nofollow">https://hurry.build</a> or self-host your own build cache service from <a href="https://github.com/attunehq/hurry" rel="nofollow">https://github.com/attunehq/hurry</a>. Sorry in advance for the rough edges - we have some customers already exercising the hot paths, but build tools are pretty large surfaces. We’ve got a list of known limitations at <a href="https://github.com/attunehq/hurry?tab=readme-ov-file#known-limitations" rel="nofollow">https://github.com/attunehq/hurry?tab=readme-ov-file#known-l...</a>.<p>We’d love for folks here to try it out (maybe on your next Rust winter side project?) and let us know what you think. We’ll be in the comments here, or you can email us at founders@attunehq.com.<p>Our goal is to make all parts of software engineering faster. If you have some part of your coding workflow that you want faster, please feel free to reach out. We’d love to chat.
Show HN: RenderCV – Open-source CV/resume generator, YAML → PDF
Show HN: RenderCV – Open-source CV/resume generator, YAML → PDF I built RenderCV because Word kept breaking my layout and LaTeX was overkill. I wanted my CV as a single YAML file (content, design, margins, everything) that I could render with one command.<p>Run <i>rendercv render cv.yaml</i> → get a perfectly typeset PDF.<p>Highlights:<p>1. <i>Version-controllable:</i> Your CV is just text. Diff it, tag it.<p>2. <i>LLM-friendly:</i> Paste into ChatGPT, tailor to a job description, paste back, render. Batch-produce variants with terminal AI agents.<p>3. <i>Perfect typography:</i> Typst under the hood handles pixel-perfect alignment and spacing.<p>4. <i>Full design control:</i> Margins, fonts, colors, and more; tweak everything in YAML.<p>5. <i>Comes with JSON Schema:</i> Autocompletion and inline docs in your editor.<p>Battle-tested for 2+ years, thousands of users, 120k+ total PyPI downloads, 100% test coverage, actively maintained.<p>GitHub: <a href="https://github.com/rendercv/rendercv" rel="nofollow">https://github.com/rendercv/rendercv</a><p>Docs: <a href="https://docs.rendercv.com" rel="nofollow">https://docs.rendercv.com</a><p>Overview on RenderCV's software design (Pydantic + Jinja2 + Typst): <a href="https://docs.rendercv.com/developer_guide/understanding_rendercv/" rel="nofollow">https://docs.rendercv.com/developer_guide/understanding_rend...</a><p>I also wrote up the internals as an educational resource on maintaining Python projects (GitHub Actions, packaging, Docker, JSON Schema, deploying docs, etc.): <a href="https://docs.rendercv.com/developer_guide/" rel="nofollow">https://docs.rendercv.com/developer_guide/</a>
No other tools from this source yet.