More explanations of missing pieces

[teekaay]

Hello, first I want to say that this is a really cool document/repo (to be future proof ;) ). To actually address the issues mentioned in "what's missing", there could be an additional section where solutions (in form of something like a concept or overview) could be displayed, either in form of small texts or links to some conceptual texts (blog or subdirectory).

Here is an example of what I mean (and this topic is the one that bothers me the most).

Unified build system

Because the build situation is so bad and tools are very isolated from each other or there are many choices, a build system in the spirit of Rust's cargo or Golang's go tool. Such a tool could unify existing tools like ocamlfind, opam, oasis etc in a single program that bundles their functionality, so less code has to be written. Of course, aspects special or unique to OCaml must be included.

Other good examples are node's npm and ruby's bundler/rake combination.

Basic features

• Configurable via JSON, TOML, ini etc
• Subcommands, e.g. build, clean, install, new/init,...
• Scripts (similar to npm scripts)
• Standards for several things, e.g. the name of the folder for auxillary files

Pro

• Pro1
• Pro2

Contra

• Contra1

etc etc.

[fxfactorial]

Please feel free to open a PR, love what you wrote. Maybe add something like another section titled Community Issues or something like that.