![]() ![]() Not to mention that a library fails to compile way more often than I'm comfortable with. If I want to add a new library to my project I have to be sure I'm willing to wait for 15-45(!!!) minutes for it to compile. It seems like the system punishes me for trying out things. If all the libraries were available for dynamic linking, wouldn't the need for recompiling simply not exist at all?Ĭurrently, one has to try really hard to stick with Haskell in these regards. I have trouble seeing why cabal hell exists in the first place. Knowing that a library doesn't support your OS BEFORE you find out for yourself.But all the problems seems insignificant to the huge benefits that you get such as There are of course drawbacks of hosting binaries like more storage space needed, multiple binaries per library for multiple OSs. ![]() NET is also compiled (to bytecode) but I can use it's DLLs without any need for recompilation. The question is, why doesn't the repository host binaries instead of just code? For example, I will never be able to run a Yesod app on my cheap VPS because the VPS isn't powerful enough to compile it and I can't really upload 500mb of precompiled libraries. I'm aware that most node dependencies do not require any compilation but I find it really strange that this isn't considered a bigger problem. If you have ever worked with pretty much any other web framework (node.js with express, for example), the process is nearly identical but takes a fraction of the time. I generate the skeleton using snap init barebones, make a new sandbox and then install the dependencies. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |