Haskell-te Alternatives

Similar projects and alternatives to haskell-te

nixpkgs

976 15,844 10.0 Nix haskell-te VS nixpkgs

Nix Packages collection & NixOS
rfcs

52 490 4.6 haskell-te VS rfcs

The Nix community RFCs (by NixOS)
InfluxDB

www.influxdata.com featured

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
repology-updater

40 477 8.9 Python haskell-te VS repology-updater

Repology backend service to update repository and package data
nixos-generators

20 1,533 8.3 Nix haskell-te VS nixos-generators

Collection of image builders [maintainer=@Lassulus]
nixos-infect

20 1,180 7.1 Shell haskell-te VS nixos-infect

[GPLv3+] install nixos over the existing OS in a DigitalOcean droplet (and others with minor modifications)
mvn2nix

3 85 2.7 Java haskell-te VS mvn2nix

Easily package your Maven Java application with the Nix package manager.
nixos-anywhere

6 1,055 8.8 Shell haskell-te VS nixos-anywhere

install nixos everywhere via ssh [maintainer=@numtide]
SaaSHub

www.saashub.com featured

SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
nix-helpers

2 8 7.5 Nix haskell-te VS nix-helpers

Mirror of http://chriswarbo.net/git/nix-helpers.git
openocd

1 4 5.9 C haskell-te VS openocd

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better haskell-te alternative or higher similarity.

Suggest an alternative to haskell-te

haskell-te reviews and mentions

Posts with mentions or reviews of haskell-te. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-08-12.

NixOS RFC 136 accepted: A plan to stabilize the new CLI and Flakes incrementally
11 projects | news.ycombinator.com | 12 Aug 2023

Yes, to get Nixpkgs it's much faster to use `fetchTarball`.
You're right that `builtins.fetchTarball` is faster than `builtins.fetchGit` (due to the ridiculous amount of commits in the Nixpkgs repo). I like to keep such definitions in a single, company-wide/project-agnostic git repo (what the Nix Pills series calls the "repository pattern"), and have individual projects import them via `builtins.fetchGit`.
Many years ago we didn't have `builtins.fetchGit`, so had to use the 'fetchgit' function from Nixpkgs instead. That created a chicken-and-egg situation if we wanted to take the Nixpkgs version from some other git repo; hence needing to "bootstrap" via `(import { config = {}; }).fetchgit`, and cross our fingers that `NIX_PATH` wasn't set to some crazy value (which, of course, I would inevitably do... https://github.com/Warbo/haskell-te/blob/24475a229908caa3447... )
Note that we need `config = {};` when importing Nixpkgs to avoid an impurity which tries to read files in $HOME. More recent versions of Nixpkgs also need `overlays = [];` to avoid another impurity (looks like this changed at Nixpkgs 17.03, according to https://github.com/Warbo/nix-helpers/blob/master/nixpkgs.nix )