google-translate
cabal-extras
Our great sponsors
google-translate | cabal-extras | |
---|---|---|
3 | 13 | |
362 | 77 | |
- | - | |
0.0 | 4.4 | |
over 1 year ago | about 1 month ago | |
Emacs Lisp | Haskell | |
- | - |
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.
google-translate
-
[Package of the day] Emacs Google Translate
There is a good alternative to this package - go-translate, to which I switched some time ago. I experienced regular errors with `google-translate`. Also `go-translate` supports multiple translation engines.
cabal-extras
-
Management of obsolete/orphaned/abandoned packages?
There's also cabal-store-gc from cabal-extras by /u/phadej. But it is still highly experimental.
-
Learning Tidal Fundamentals - nice ground-up intro to TidalCycles by Mark Zadel
I've not completely got my head around it, but I think it's more about bugs and missing features. Tidal users don't work in 'projects' or 'packages', they just want to install a library and then use it in the interpreter. There's a fundamental difference between programming to make something and programming as the end in itself, and cabal doesn't seem to consider the latter use case. It seems the cabal-env prototype does support this (sitting here: https://github.com/phadej/cabal-extras) but it hasn't been merged into cabal itself yet. In the meantime v1-install works pretty well, or at least a lot better than v2-install, which just seems buggy to me, but I'm told I'm just trying to use it the wrong way.
-
[Request for review] Short article on Cabal and Stack and difference between them
Cabal also has some support for offline builds, the cabal-extras project has a bundle command to curl the dependencies into a bundle. https://github.com/phadej/cabal-extras The build artefact aren't necessarily portable across machines.
-
Trouble with cabal.
If you want to use cabal (which has various advantages over stack, although as it has access to whole hackage some times requires a bit more thinking) i'd suggest to install cabal-env. Its an experimental tool, written by previous maintainer of cabal. You can simply run cabal install cabal-env to get it. Its part of https://github.com/phadej/cabal-extras. It is what cabal install --lib is supposed to be (and likely will become at some point).
-
There is no cabal hell.
Cabal 3.x and nix-style builds is a partial improvement, however it still suffers its legacy, with some of the most fundamental issues unsolved or even not addressed. For example maintenance of installed packages in long runs, stale or broken packages from previous failed builds impede the workings etc. Suggested fix is usually to wipe-out whole storage and rebuild everything from scratch again sic. Even when you are lucky, like avoiding update of ghc at all costs, with new base breaking almost everything, you'll soon end up with tenths or hundreds of gigabytes wasted disk space and significantly slower operations, with half of whole Hackage packages in its their countless iterations. I would already gave up completely, unless I've run across phadej's cabal-extras, which with some minor fixes save my sanity.
-
Need help with installing modules
You can install libraries separately with cabal install --lib ..., but the default way is kind of broken. There is an experimental cabal-env tool which works much better, but it is experimental so it is hard to recommend to a beginner.
-
Why is Stack rebuilding everything?
If you are willing to use cabal then the cabal-extra library has some support for offline builds via cabal-bundle https://github.com/phadej/cabal-extras
What are some alternatives?
strive - :bicyclist: A Haskell client for the Strava V3 API.
Cabal - Official upstream development repository for Cabal and cabal-install
heist - An xhtml-based templating engine, allowing Haskell functions to be bound to XML tags.
cache-s3
google-cloud
hw-kafka-avro - SchemaRegistry bindings with Avro scheme to use with kafka-client
google-maps-geocoding - Haskell bindings to the Google Maps Geocoding API
haskell-handbook - Best practices on how to be efficient with Haskell in production
line-bot-sdk - ð¥HaskellåãLINE Messaging API SDK
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
cabalgc - Selectively remove library packages in cabal store.
themoviedb - Simple Haskell library that provides functions for retrieving movie metadata from TheMovieDB