amazonka
Cabal
amazonka | Cabal | |
---|---|---|
7 | 84 | |
589 | 1,566 | |
- | 0.4% | |
9.5 | 9.8 | |
about 1 month ago | about 8 hours ago | |
Haskell | Haskell | |
Mozilla Public License 2.0 | GNU General Public License v3.0 or later |
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
Cabal
-
Would anyone be interested in hoot: A cabal wrapper for haskell based on Cargo?
Also, there's already a cabal RFC to support toml: https://github.com/haskell/cabal/issues/7548
-
On the verge of giving up learning Haskell because of the terrible tooling.
Cabal has a lot of dark corners once you stray from the happy path. Just checked and I'm currently subscribed to 37 threads on the issue tracker, and I'm not a maintainer. A lot of these are related to lesser-used features like cabal scripts, environment files and doctests (though I think all of these things would used more if they were more reliable), but there's also plenty of stupid stuff like: - https://github.com/haskell/cabal/issues/3313 - https://github.com/haskell/cabal/issues/8527 - https://github.com/haskell/cabal/issues/8391 - https://github.com/haskell/cabal/issues/7789 - https://github.com/haskell/cabal/issues/6888 - https://github.com/haskell/cabal/issues/6999 - https://github.com/haskell/cabal/issues/5271
-
Problems installing hindent witch haskell tool stack on windows 10
Given that Mike Pilgrim (the Stack maintainer) is on Windows, and Cabal has issues on Windows, I think it might be easier to get Windows specific fixes merged in Stack.
-
Help figuring out output from Cabal resolver
The error message is not too helpful. This is the target of a long-standing ticket: https://github.com/haskell/cabal/issues/7993 Your help would be very welcome.
-
There is No “Tooling Issue” in Haskell
By the way, there are some open issues for the command to add a package in Cabal.
-
Why GHCi is my new calculator
That's interesting. Could you could open a an issue about this? https://github.com/haskell/cabal/issues
- Any open source projects to contribute to for beginners
-
The best way to add a flag to copy documentation to given location?
I created this issue a few months ago: https://github.com/haskell/cabal/issues/8270
-
Trying to figure out cabal dependency management
Reported this as a bug in cabal.
-
JavaScript backend merged into GHC | IOG Engineering
We definitely plan to have benchmarks once we start working on performance. We haven't started yet because there were more urgent tasks. For example: ensuring that the testsuite runs on CI with the JS backend (should be completed this week or the next), ensuring that the toolchain works properly (we're writing a tutorial and we've found new bugs, e.g. yesterday I've fixed the support for js-sources in Cabal https://github.com/haskell/cabal/pull/8636), adding TH support...
What are some alternatives?
aws-ec2 - Now maintained by: See https://github.com/memcachier/aws-ec2
stack - The Haskell Tool Stack
amazonka-s3-streaming - Provides a conduit based interface to uploading data to S3 using the Multipart API
haskell.nix - Alternative Haskell Infrastructure for Nixpkgs
aws - Amazon Web Services for Haskell
static-haskell-nix - easily build most Haskell programs into fully static Linux executables
amazon-emailer - A simple daemon to process messages put into a postgresql table and mail them out using amazons SES.
cartel
hs-GeoIP - Haskell bindings to the MaxMind GeoIPCity database
hackage-repo-tool - Hackage security framework based on TUF (The Update Framework)
aws-lambda - Haskell bindings for AWS Lambda
codeworld - Educational computer programming environment using Haskell