unicode-transforms VS hnix

Compare unicode-transforms vs hnix and see what are their differences.

unicode-transforms

Fast Unicode normalization in Haskell (by composewell)

hnix

A Haskell re-implementation of the Nix expression language (by haskell-nix)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
unicode-transforms hnix
1 4
47 726
- 1.7%
2.5 6.8
5 months ago 21 days ago
Haskell Nix
BSD 3-clause "New" or "Revised" License BSD 3-clause "New" or "Revised" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

unicode-transforms

Posts with mentions or reviews of unicode-transforms. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-04-17.
  • [ANN] unicode-collation 0.1
    3 projects | /r/haskell | 17 Apr 2021
    Thanks! Here's a puzzle. Profiling shows that about a third of the time in my code is spent in normalize from unicode-transforms. (Normalization is a required step in the algorithm but can be omitted if you know that the input is already in NFD form.) And when I add a benchmark that omits normalization, I see run time cut by a third. But text-icu's run time in my benchmark doesn't seem to be affected much by whether I set the normalization option. I am not sure how to square that with the benchmarks here that seem to show unicode-transforms outperforming text-icu in normalization. text-icu's documentation says that "an incremental check is performed to see whether the input data is in FCD form. If the data is not in FCD form, incremental NFD normalization is performed." I'm not sure exactly what this means, but it may mean that text-icu avoids normalizing the whole string, but just normalizes enough to do the comparison, and sometimes avoids normalization altogether if it can quickly determine that the string is already normalized. I don't see a way to do this currently with unicode-transforms.

hnix

Posts with mentions or reviews of hnix. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-01-06.
  • Good Haskell Source Code
    5 projects | /r/haskell | 6 Jan 2022
    I also can nominate HNix: https://github.com/haskell-nix/hnix. Nix is a lazy pure language, HNix is an implementation of Nix in lazy pure language (Haskell). The project was done by a famous expert in the field of compilers/interpreters, which worked on Borland C++ compiler back in a day. The project overall was done by a pretty start team.
  • Tvix: We are rewriting Nix
    2 projects | /r/NixOS | 3 Dec 2021
    Well, maintaining a rewrite of Nix in Haskell: https://github.com/haskell-nix/hnix.

What are some alternatives?

When comparing unicode-transforms and hnix you can also consider the following projects:

massiv - Efficient Haskell Arrays featuring Parallel computation

safecopy - An extension to Data.Serialize with built-in version control

abcBridge - Haskell bindings for ABC

hashable - A class for types that can be converted to a hash value

b-tree - Haskell on-disk B* tree implementation

primitive - This package provides various primitive memory-related operations.

compact - Compact regions library for Haskell

scientific - Arbitrary-precision floating-point numbers represented using scientific notation

thyme

tagged - phantom types

bifunctors - Haskell 98 bifunctors, bifoldables and bitraversables

avro - Haskell Avro Encoding and Decoding Native Support (no RPC)