amazonka
bytestring
Our great sponsors
amazonka | bytestring | |
---|---|---|
7 | 15 | |
588 | 282 | |
- | 0.7% | |
9.5 | 7.9 | |
14 days ago | 9 days 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
bytestring
-
RunWithScissors() (2009)
The documentation is itself fairly funny, for those who don’t care to click ahead:
> This "function" has a superficial similarity to ‘unsafePerformIO’ but it is in fact a malevolent agent of chaos. It unpicks the seams of reality (and the IO monad) so that the normal rules no longer apply. It lulls you into thinking it is reasonable, but when you are not looking it stabs you in the back and aliases all of your mutable buffers. The carcass of many a seasoned Haskell programmer lie strewn at its feet.
> Witness the trail of destruction:
https://github.com/haskell/bytestring/commit/71c4b438c675aa360c79d79acc9a491e7bbc26e7
-
Monthly Hask Anything (July 2022)
If you bring in efficient strings from bytestring, densely packed arrays from vector, and an in-place sort from vector-algorithms, you can bring it down to 275ms (uses 19MB of mem).
- Some light investigation regarding ByteString's IsString instance, and its conclusions
-
Haskell - Important Libraries
bytestring
-
[ANNOUNCE] GHC 9.2.2 is now available!
Note that this release is broken for Windows.
-
Beginner level tutorial - bytestring
I've opened https://github.com/haskell/bytestring/issues/455 so the situation can be improved. You're very welcome to chime in on the discussion or to contribute some of the missing documentation yourself! :)
-
bytestring-0.11.2.0
Highlights from the changelog:
- [Haskell]
-
Dragging Haskell Kicking and Screaming into the Century of the Fruitbat :: Reasonably Polymorphic
Well, ByteString in particular should not have an IsString instance in a new report. That's pretty clear by https://github.com/haskell/bytestring/issues/140 : the concensus is that there is no good solution right now, but it should not have gotten an IsString instance in the first place. If a theoretical new Haskell Report 202x includes OverloadedStrings (as it should) to handle string literals analogously to numeric literals, I'd expect it to not give ByteString (which is really just a collection of octets) an IsString instance, with all it's issues and rattail due to the encoding question being implicitized.
-
How can Haskell programmers tolerate Space Leaks?
Standard streaming libraries. They are being written by people that make the effort to understand performance and I have a hope that they make sure their streams run in linear space under any optimizations. It is curious and unsettling that we have standard lazy text and byte streams at the same time — and the default lazy lists, of course. I have been doing some work on byte streams and what I found out is that there is no way to check that your folds are actually space constant even if the value in question is a primitive, like say a byte — thunks may explode and then collapse over the run time of a single computation, defying any effort at inspection.
What are some alternatives?
aws-ec2 - Now maintained by: See https://github.com/memcachier/aws-ec2
bytestring-read - fast ByteString to number converting library
amazonka-s3-streaming - Provides a conduit based interface to uploading data to S3 using the Multipart API
bytestring-typenats - Haskell ByteStrings annotated with type-level naturals for lengths
aws - Amazon Web Services for Haskell
bytestring-builder - The new bytestring builder, packaged outside of GHC
amazon-emailer - A simple daemon to process messages put into a postgresql table and mail them out using amazons SES.
bytestring-tree-builder - A very efficient ByteString builder implementation based on the binary tree
hs-GeoIP - Haskell bindings to the MaxMind GeoIPCity database
bytestring-delta - Simple binary diff/patch library for C and Haskell
aws-lambda - Haskell bindings for AWS Lambda
bytestring-plain - Plain byte strings (`ForeignPtr`-less `ByteString`s)