amazonka
jrec
Our great sponsors
| amazonka | jrec | |
|---|---|---|
| 7 | 1 | |
| 588 | 35 | |
| - | - | |
| 9.5 | 3.2 | |
| 14 days ago | about 1 year ago | |
| Haskell | Haskell | |
| Mozilla Public License 2.0 | BSD 3-clause "New" or "Revised" License |
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.
amazonka
-
Getting Amazonka S3 to work with localstack
This is perhaps not as obvious as it could be. A penny for your thoughts? https://github.com/brendanhay/amazonka/issues/968
- amazonka 2.0.0-rc2 announced
-
[JOB] Haskell Developer @ Bellroy (Remote)
Most of our tech stack is built on Free and Open Source Software, and we give back wherever we can - either by upstreaming fixes or publishing libraries. In the Haskell world, we’ve open-sourced wai-handler-hal and aws-arn, made significant contributions to amazonka and we have more on the way. If you’re interested, here’s our applications page. If you have questions, you can ask them here or email [[email protected]](mailto:[email protected]).
-
stack
Stack does not clone a copy of a git package for each of a user's projects that uses the package but cabal does. This can be a deal-breaker for cabal when using huge git projects like https://github.com/brendanhay/amazonka that can take forever to git clone. If you have a test/CI setup for a project that uses such packages, cabal's lack of caching can also cause huge delays and more opportunities for failure (from network errors or timeouts). From the proceedings of past issues, I don't think cabal devs are interested in addressing this use case. https://github.com/haskell/cabal/issues/5586
- Usability of smart constructors and large records with required, optional, and default parameters
- Amazonka 2.0.0-rc1 is ready for testing
-
Haskell ghost knowledge; difficult to access, not written down
amazonka is a bit of a minefield despite being listed as the only AWS library by SOTU
jrec
-
Haskell ghost knowledge; difficult to access, not written down
Try jrec. I threw away the sorting and it typechecks much faster now.
What are some alternatives?
aws-ec2 - Now maintained by: See https://github.com/memcachier/aws-ec2
regex-tdfa - Pure Haskell Tagged DFA Backend for "Text.Regex" (regex-base)
amazonka-s3-streaming - Provides a conduit based interface to uploading data to S3 using the Multipart API
rawr - Anonymous extensible records and variant types
aws - Amazon Web Services for Haskell
text-icu - This package provides the Haskell Data.Text.ICU library, for performing complex manipulation of Unicode text.
amazon-emailer - A simple daemon to process messages put into a postgresql table and mail them out using amazons SES.
superrecord - Haskell: Supercharged anonymous records
hs-GeoIP - Haskell bindings to the MaxMind GeoIPCity database
post-rfc - Blog post previews in need of peer review
aws-lambda - Haskell bindings for AWS Lambda
loup - Simple Workpools