3 ms·
> You find Ocaml libs for a lot of needs, but a lot of those a unmaintained and have their last commit a couple of years ago. Not sure what issues you ran into
by gabipurcaru 8y ago
> You find Ocaml libs for a lot of needs, but a lot of those a unmaintained and have their last commit a couple of years ago.
Not sure what issues you ran into, but this isn't necessarily a bad thing. I had a similar experience with Elixir, where some libraries had been last touched two years ago, but did the job with no issues whatsoever.
- raphinou 8y agoWell, one example is oauth in ocaml. I find this https://github.com/jaked/ooauth https://github.com/jaked/ooauth but it has an open issue from 2013 titled "Fix compilation on recent ocamlnet, gcc". I have the feeling I encounter a lot of these situations when I look at libraries I would need for a project. It's rather uncommon I see a very active project in Ocaml (even if there are some indeed).
- donatj 8y agoThis is something I see and feel often. If something is untouched, that doesn’t mean it’s broken or for that matter unmaintained. It can simply mean it was simply done correctly from the get go. Think of code as a formula, how many formulas are there that haven’t been touched in hundreds of years, due to the fact that they are correct. The desire for libraries that are constantly in flux stems from the “move fast and break things” mentality, mixed with the continuous flow of breakage in mutable languages. If you move slow and do things well, you can often build some reliable with a fraction of the effort.
- thrower123 8y agoI would agree. I'm happier using a stable, rarely changing library than something that is in constant flux and changing every week. Really, that kind of breakneck pace signals to me that people are just throwing stuff at the wall to see what sticks, and reduces my confidence in the quality of the product...