aeson
A fast Haskell JSON library (by haskell)
Our great sponsors
| Haskell-breaking-changes | aeson | |
|---|---|---|
| 3 | 9 | |
| 88 | 1,227 | |
| - | 0.3% | |
| 0.0 | 7.0 | |
| over 2 years ago | 20 days ago | |
| Haskell | ||
| - | GNU General Public License v3.0 or later |
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.
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.
Haskell-breaking-changes
Posts with mentions or reviews of Haskell-breaking-changes.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-13.
aeson
Posts with mentions or reviews of aeson.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-24.
-
Haskell adoption is higher than I expected, what can we do to get it to top 10 languages.
Don't get me wrong, we figured it all out, and currently we use Aeson fork as we needed this: https://github.com/haskell/aeson/pull/926, as the default behaviour didn't work with Swift, and I wasn't sure if it's worth spending any time completing it...
-
PSA: aeson hash flood vulnerability was assigned CVE-2022-3433
See PR 871 and PR 877 for when and how exactly these things changed.
- kodimensional :: Avoiding space leaks at all costs
-
How would aeson redesign FromJSON without intermediate Value?
Simdjson-based Hermes is able to decode JSON significantly faster while still using an intermediate representation: https://github.com/haskell/aeson/pull/923
- List of upcoming breaking changes
-
The aeson vulnerability has been fixed in aeson-2.0.1.0
Ah, I see you are working on this already, thank you: https://github.com/haskell/aeson/pull/883
-
Text Maintainers: text-utf8 migration discussion - Haskell Foundation
Similar scan is already in aeson https://github.com/haskell/aeson/blob/master/src/Data/Aeson/Parser/Internal.hs#L322-L335 where the unsafeDecodeASCII is used I mentioned in my previous comment.
-
High-performance JSON codec
Well, the aeson’s ffi code is written by me: https://github.com/haskell/aeson/commit/2f24e555d86a36fdda6d4cad79976004b382ab3b
What are some alternatives?
When comparing Haskell-breaking-changes and aeson you can also consider the following projects:
foundation - Empire strikes back
aeson-coerce
streaming-commons - Common lower-level functions needed by various streaming data libraries
alternative-vector - Use vectors with many and some, instead of lists
cryptonite - lowlevel set of cryptographic primitives for haskell
aeson-utils - Utilities for working with aeson.
wai-conduit - Haskell Web Application Interface
aeson-applicative - define To/From JSON instances from one applicative definition
iproute - IP Routing Table in Haskell
req - An HTTP client library
cereal
tmp-postgres - Create temporary postgres instances
Haskell-breaking-changes vs foundation
aeson vs aeson-coerce
Haskell-breaking-changes vs streaming-commons
aeson vs alternative-vector
Haskell-breaking-changes vs cryptonite
aeson vs aeson-utils
Haskell-breaking-changes vs wai-conduit
aeson vs aeson-applicative
Haskell-breaking-changes vs iproute
aeson vs req
Haskell-breaking-changes vs cereal
aeson vs tmp-postgres