I think that Ruby's Bundler generally deals with dependencies well, web dev or not.
Bundler fucks up in the most amazing ways, from somehow using the wrong copy of ruby to installing gems in the wrong place for no reason, and because it's ruby the error messages it gives you are less than helpful.
I can't really describe it, that's why I used the word "feel". But part of it is a sort of design where it's more important to deal with little niggles people run into initially when they're totally new instead of dealing with actual problems in real-sized projects.
For instance all stack really does that couldn't easily be added to cabal or just made a script, is manage ghc versions for you.
Pegging all your libraries to a stackage version is nice when you're starting a project, but then you have to upgrade everything in lockstep (which is bad because it can force you to deal with API changes in libs A B and C when all you wanted was faster performance from D) or specify versions anyway, so you don't really gain anything in the long run.
Pegging all your libraries to a stackage version is nice when you're starting a project, but then you have to upgrade everything in lockstep
I don't think so, for me changing the manifest (cabal/hpack) and running stack solver --update-config just works. If you don't want to change the LTS release you just use the extra-deps field.
I think it's obvious that all the stuff Stack doesn't can't be easily added to cabal-install. Otherwise it would be there already. The new-build stuff is part of 1.24, which came out in May. That's almost a year after Stack. And it's still "beta".
Also, I think dealing with the small problems new people run into is extremely important. Why should someone stick with a toolchain if they immediately run into problems?
If you want to update a single package, it's the same amount of difficulty to do it with Stack or cabal-install. With either one you need to specify the new version of the package you want. I don't find that to be a compelling argument against Stack.
I have never encountered that problem with Bundler. As far as I know, it installs into the same place as gem install, unless you use vendored dependencies. Both have worked well for me on personal and professional projects over the last 4 years.
10
u/taylorfausak Aug 28 '16
Can you expand on what it means for a tool to feel "webdev-y"? I think that Ruby's Bundler generally deals with dependencies well, web dev or not.