unicode-transforms VS jump

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

jump

Jump start your Haskell development (by commercialhaskell)
InfluxDB - 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.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
unicode-transforms jump
1 -
47 158
- 0.0%
2.5 0.0
6 months ago over 7 years ago
Haskell
BSD 3-clause "New" or "Revised" License MIT 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.

jump

Posts with mentions or reviews of jump. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning jump yet.
Tracking mentions began in Dec 2020.

What are some alternatives?

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

with-utf8 - Get your IO right on the first try

stdf - Parse Structured Test Data Format in Haskell

refined - Refinement types with static checking

semantic-source - Parsing, analyzing, and comparing source code across many languages

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

thyme

code-builder - Packages for defining APIs, running them, generating client code and documentation.

gps2htmlReport - Generates a HTML page report detailing a GPS journey, with charts, statistics and an OpenStreetMap graphic.

critbit - A Haskell implementation of crit-bit trees.

HaLeX

hnix - A Haskell re-implementation of the Nix expression language

cereal