book VS Fable: F# |> BABEL

Some of your questions might be answered in this book (free online version): https://dev.realworldocaml.org/

I don't think they're wrong

the Jane Street side are quite prolific with blog posts etc

as a newcomer to OCaml one of the first, and nicer-looking, intro resources you'll likely encounter is the Real World OCaml book https://dev.realworldocaml.org/ which unfortunately does everything using Base instead of the stdlib

Personally that didn't sit right to me and I prefer to use the stdlib by default (which seems fine and not in need of a wholesale replacement)

This is an oldie but a goodie.

OCaml has, unlike Standard ML, grown quite a lot since this page was made.

In particular, the section "Standard libraries", I'd recommend looking at:

https://dev.realworldocaml.org/

A couple of places where the comparison is outdated:

- OCaml using Base [1] allows for result-type oriented programming

- OCaml using Base uses less language magic and more module system

While there was and is truth to the distinction that SML is for scientists and OCaml is for engineers, this dichotomy is getting dated: OCaml is under active development, which means that scientists who want better tooling will choose OCaml. For example, 1ML [2] by Andreas Rossberg was built in OCaml.

[1]: https://opensource.janestreet.com/base/

Real World OCaml (version 2 is finally out) is also pretty good.

Real World OCaml is also a good resource, geared more towards people who already have some programming experience and want a more industry/practical focused learning experience.

ocaml.org’s new website is packed with lots of great early intros.

most learners eventually gravitate towards Real World OCaml https://dev.realworldocaml.org/ for additional learning.

Unfortunately, the learning resources for different domains out there isn’t as highly curated or prolific as, say, rust. If you do web dev like me, it takes a bit more work to find the tools and put them together. But the language itself lends itself well to systems level programming.

Fortunately, the forum is a great help.

In general, better read the second edition which is updated to use current Core versions. A print version was published recently.

I recommend https://dev.realworldocaml.org/ and https://cs3110.github.io/textbook/cover.html

Elm is not dead. It just prefers a slow release schedule but is still actively worked on in the background.

That said, you might want to check out OCaml for general purpose programming. Super fast compiler, great performance, can target both native and JS.

It is easier to use than Haskell due to defaulting to eager evaluation (like most languages) strategy instead of laziness and being generally more pragmatic, offering more escape hatches into the imperative world if need be. Plus great upward trajectory with lot's of cool stuff like an effects system and multi-core support coming.

Real World Ocaml is a decent resource: https://dev.realworldocaml.org/

This conversation could be referring to https://fable.io/

Other than that, the question is indeed strange and I agree with your statements.

NOTE: For larger codebases with more history it is likely that the Program.fs file will have a lot of orchestration and logic as well. given that it is often where everything clashes and starts, for example the Fable Entrypoint is in Entry.fs and it contains a lot of code. The best you can do always is to start at the bottom of the file and work your way up. Remember: Everything at the bottom uses what has already been defined at the top so there are no circular dependencies or random functions/types at the bottom that can trip you off, everything comes from the top!

I am a big fan of going with web components + plain (build-less) javascript whenever possible, so it is not surprising that I often favor things like the Fable Compiler, where I can target my F# code directly to javascript and be as close to the native JS experience as possible, both for interop concerns and for ecosystem integration.

Fable compiler - https://fable.io/

The F# community is very friendly (these sub-communities as well), and they have plenty of good issues/opportunities to contribute OSS work to across any skill level.

Phosphor isn't hiring right now, but we expect to begin a search for FE/interface engineers over the next few month. Email [email protected] for anyone interested.

Naturally I’d recommend using a better language such as ReScript or Elm or PureScript or F#‘s Fable + Elmish, but “React” is the king right now and people perceive TypeScript as “less risky” for jobs/hiring, so here we are.

Stuff like this: https://github.com/fable-compiler/Fable/issues/1822

It just seems like an incredibly ambitious project that appears to have very little equal but is mainly worked on by a handful of people but no corporate backing. I get the feeling that if you want to use it, you'll either be the only one doing what you're doing or among just a few people. I already use F# and feel this way about the core language itself.

F# is also part of the OCaml family, has a great to-JS transpiler (https://fable.io/) and F# code can also be used in .NET projects.

I have heard many good things about https://fable.io/ Fable converts F# code to JavaScript. There are currently 407 packages available for interacting with existing JavaScript packages and frameworks.