OCaml 2016 — The State of the Hump
It’s 2016 and we all know functional programming is the path forward. From ReactJS, Elixir, MirageOS, Docker, and Facebook flow to Elm, this style of programming is clearly being widely adopted and needed.
Getting to the Next Stage
merlin were desparately needed and got us to what past the what I’d call the first hump, but now we need to get past the second hump; to capture that group of programmers that just need to have a
What’s missing for wide spread adoption
Here’s the TODO list, order doesn’t mean priority.
These issues also overlap with why a typical SV startup might hesitate to pick OCaml (Some of these issues are being worked on).
An actual ORM. Wrong or right they get stuff done. A nice feature would be something that used a PPX extension to generate type safe SQL and functorized over a backend, starting with
Postgresql. Just hasn’t been done. There are things that approximate this but they have various short comings in their own way. Maybe something like
[@@deriving pg_insert, pg_select](thanks
Typical middleware needed for web application backends. We need something like
nodejs‘s express. Something that instantly handles 30k+ connections, like I can with 30 lines of
Documentation, documentation, documentation. We have amazing tools like
js_of_ocamlbut the documentation is lacking and only the most determined hackers stay.
A web framework in the spirit of Django or Rails. (And please not something that reaches
Yesodlevels of mental abstraction).
ReactJS, that would be ideal.
Namespaces. This is a problem right now, name something
dispatch.mland use a transitive dependency that also defines dispatch. Boom.
A friendlier attitude towards web development. Many people still think web coding is lame or not serious. That’s wrong, web programming is amazing and much innovation comes out of web programming.
Core libs like
Lwtneed love and care, and there are simply not enough hands to go around at the moment and that’s a real shame since big projects like
mirageare built on top of
Marketing. Haskell blows us out of the water in name recognition, and there’s no reason why we can’t have that level of recogition as well.
The build situation is pretty bad. We have too many build tools with no consensus on building code. Explaining all of them at once to programmers coming from interpreted languages is a big time suck.
A non-monadic HTTP library, maybe
The more people we can get into OCaml, the more these problems go away -> more people means more $$$ and hands.
The OCaml community is made up of many friendly and incredibly talented people. I’m sure we can overcome these difficulties. 2016 is going to be OCaml’s year, no doubt.
转载本站任何文章请注明：转载至神刀安全网，谢谢神刀安全网 » An OCaml manifesto – Problems and what's needed for widespread adoption