Jane Street releases open source alternative to OCaml's stdlib
ocaml.janestreet.com
Jane Street releases open source alternative to OCaml's stdlib
1–10 of 13 posts
Re: Jane Street releases open source alternative to OCaml's stdlib
#2Re: Jane Street releases open source alternative to OCaml's stdlib
#3Just a note, this is an announcement that they've but their corelib on bitbucket, the library itself has been available from janestreet for years.
Also, this release includes Async (our concurrency library), which is a much more recent release (October 2011). If you'd like more information about Async, there's Ron's blog post announcing the release [1], and also a previous comment of mine with some very basic sample Async code [2].
Re: Jane Street releases open source alternative to OCaml's stdlib
#4Just a note, this is an announcement that they've but their corelib on bitbucket, the library itself has been available from janestreet for years.
While this is mostly true, it's worth noting that this is part of a push to make Core easier to build and use, which we hope will encourage more people to use it. (And enable others to contribute.) There's still a ton of work to be done in that regard, but this release, at least, includes a Linux build script, and the libraries which are necessary for building Core. Also, this release includes Async (our concurrency…
Re: Jane Street releases open source alternative to OCaml's stdlib
#5Earlier quoted context omitted.
While this is mostly true, it's worth noting that this is part of a push to make Core easier to build and use, which we hope will encourage more people to use it. (And enable others to contribute.) There's still a ton of work to be done in that regard, but this release, at least, includes a Linux build script, and the libraries which are necessary for building Core. Also, this release includes Async (our concurrency…
What was the initial motivation for writing an alternative "standard" library? Is it self-sufficient or does it build new frameworks onto of OCaml's standard library?
Probably the biggest difference between Core and the INRIA (default) standard library is that Core itself is mostly written in OCaml. This has many benefits: code is less verbose, easier to read, it's easier to verify correctness, etc.
Re: Jane Street releases open source alternative to OCaml's stdlib
#6Earlier quoted context omitted.
While this is mostly true, it's worth noting that this is part of a push to make Core easier to build and use, which we hope will encourage more people to use it. (And enable others to contribute.) There's still a ton of work to be done in that regard, but this release, at least, includes a Linux build script, and the libraries which are necessary for building Core. Also, this release includes Async (our concurrency…
What was the initial motivation for writing an alternative "standard" library? Is it self-sufficient or does it build new frameworks onto of OCaml's standard library?
Related links:
Core: https://bitbucket.org/yminsky/ocaml-core/wiki/Home Batteries: https://github.com/ocaml-batteries-team/batteries-included
Re: Jane Street releases open source alternative to OCaml's stdlib
#7Earlier quoted context omitted.
What was the initial motivation for writing an alternative "standard" library? Is it self-sufficient or does it build new frameworks onto of OCaml's standard library?
The std-lib in OCaml's official release by INRIA is very basic and not enough to be used in medium/large projects, and some people would rather call it "base-lib" instead of "std-lib" . Two major libraries can be used as an alternative, i) Jane Street's Core libraries. and ii) the comunity-driven "Batteries included". Related links: Core: https://bitbucket.org/yminsky/ocaml-core/wiki/Home Batteries: https://github.co…
I've been interested in OCaml for a good few years now and have tinkered with it from time to time, but I think its time I gave it serious try.
Re: Jane Street releases open source alternative to OCaml's stdlib
#8Earlier quoted context omitted.
The std-lib in OCaml's official release by INRIA is very basic and not enough to be used in medium/large projects, and some people would rather call it "base-lib" instead of "std-lib" . Two major libraries can be used as an alternative, i) Jane Street's Core libraries. and ii) the comunity-driven "Batteries included". Related links: Core: https://bitbucket.org/yminsky/ocaml-core/wiki/Home Batteries: https://github.co…
For someone just starting out with OCaml, what are the pros and cons of one over the other? (or which would you recommend and why?) I've been interested in OCaml for a good few years now and have tinkered with it from time to time, but I think its time I gave it serious try.
Second, As no better than someone "just starting out with OCaml" myself, I'd like to redirect you to this page on StackOverflow for a comparison between Batteries and Core:
http://stackoverflow.com/questions/3889117/what-are-the-pros....
Re: Jane Street releases open source alternative to OCaml's stdlib
#9* Marking partial functions with some naming convention
* Polymorphic containers, with polymorphic "length" and other features people take for granted
* Removing monomorphic functions such as "map" and "empty" -- expose APIs almost always as part of generic classes
* type String = Text (Along with extra polymorphism it should not cause any trouble)
* Sane numeric hierarchy that matches the mathematical definition
* Fix the Monad/Applicative duplication mess (Also remove "fail" from Monad)
Re: Jane Street releases open source alternative to OCaml's stdlib
#10I wish someone capable authored a Haskell standard library replacement. It could have many improvements: * Marking partial functions with some naming convention * Polymorphic containers, with polymorphic "length" and other features people take for granted * Removing monomorphic functions such as "map" and "empty" -- expose APIs almost always as part of generic classes * type String = Text (Along with extra polymorphi…
Personally, I'd think Hackage getting some kind of support for popularity metrics would go some way to solving this problem, by helping create a consensus of what packages used the most by the Haskell community.