I can see the same thing happening everywhere from JavaScript, through Ruby and Racket to Haskell. We are slowly moving towards a distributed maintainership of the base library. I consider this to be a good thing, but we currently do not have the tools required to organize such a large system.
In the Haskell world the libraries are getting organized according to their meaning and function, rather than their name. Observe for example the contravariant package.
We could adopt the proven Linux distribution system:
integrate and ship everything every n months;
maintain at least n*2 months;
automate the dependency discovery.
Or we could start bundling things. It’s our choice.
I think this was posted before here on lobste.rs, but it seems to always be relevant when discussing dependencies as a possible way out of this current “mess”. It is not hip, but it works.
I wouldn’t call the Linux approach proven. If anything I’d say the proliferation of distributions has held Linux back, and the tendency to integrate everything at the distribution-release level has lead many developers to look elsewhere, or else deliberately avoid using the distribution package manager during development.
The LTS snapshots minimize the amount of ad-hoc dependency resolution required for a build as well. Works better than I though it would when it was announced. I’ve really enjoyed using Stack for my work.
Hey, I read you and you are awesome. I need to check people profiles a bit more often. :-)
Weird thing is that I have some intangible problem with stack. It may well be that I am still learning and they seem to be quite complex. Also, I did not wanted to sound like I was pushing Haskell as an example for how JavaScript world should organize itself. I never did any serious work in this domain.
Weird thing is that I have some intangible problem with stack. It may well be that I am still learning and they seem to be quite complex.
Not sure what you mean, but my coauthor Julie and I made a tutorial video at https://www.youtube.com/watch?v=sRonIB8ZStw it’s longer than it needs to be, the basics are covered in the first 30 or so minutes. Hope it helps, if not, you could tell me what’s giving you grief.
And of course, an npm module to consume the API.
Probably has something to do with the left-pad post.
I can see the same thing happening everywhere from JavaScript, through Ruby and Racket to Haskell. We are slowly moving towards a distributed maintainership of the base library. I consider this to be a good thing, but we currently do not have the tools required to organize such a large system.
In the Haskell world the libraries are getting organized according to their meaning and function, rather than their name. Observe for example the contravariant package.
We could adopt the proven Linux distribution system:
Or we could start bundling things. It’s our choice.
http://enricozini.org/blog/2014/debian/debops/
I think this was posted before here on lobste.rs, but it seems to always be relevant when discussing dependencies as a possible way out of this current “mess”. It is not hip, but it works.
Nice one. I can totally relate to him.
I wouldn’t call the Linux approach proven. If anything I’d say the proliferation of distributions has held Linux back, and the tendency to integrate everything at the distribution-release level has lead many developers to look elsewhere, or else deliberately avoid using the distribution package manager during development.
https://www.stackage.org/ has LTS snapshots which is a package set and compiler version guaranteed to work together and pass tests as a group.
https://github.com/commercialhaskell/stack is the usual way of taking advantage of Stackage LTS, although you can turn them into a Cabal freeze as well.
The LTS snapshots minimize the amount of ad-hoc dependency resolution required for a build as well. Works better than I though it would when it was announced. I’ve really enjoyed using Stack for my work.
I know.
Not everyone else does.
Hey, I read you and you are awesome. I need to check people profiles a bit more often. :-)
Weird thing is that I have some intangible problem with
stack. It may well be that I am still learning and they seem to be quite complex. Also, I did not wanted to sound like I was pushing Haskell as an example for how JavaScript world should organize itself. I never did any serious work in this domain.Not sure what you mean, but my coauthor Julie and I made a tutorial video at https://www.youtube.com/watch?v=sRonIB8ZStw it’s longer than it needs to be, the basics are covered in the first 30 or so minutes. Hope it helps, if not, you could tell me what’s giving you grief.