ClojureCLR VS F#

Before Rich made Clojure for the JVM, he wrote dotLisp[1] for the CLR. Not long after Clojure was JVM hosted, it was also CLR hosted[2]. One of my first experiences with ML was F#[3], a ML variant that targets the CLR. These all predate the MIT licensed .net, but prior to that there was mono, which was also MIT licensed.

1: https://dotlisp.sourceforge.net/dotlisp.htm

2: https://github.com/clojure/clojure-clr

3: https://fsharp.org/

Yea, that's true. I forgot about that. I did think of Clojure CLR, but I don't get the impression that this is an all that natural or used implementation. ClojureScript is obviously much more used, although it is still a "different" language.

https://github.com/clojure/clojure-clr

ClojureCLR can already run on .NET 5.0 , so at least it made it through the .NET Core migration. I'm sure they'll get it to 6.0 at some point.

https://github.com/clojure/clojure-clr/wiki/Getting-started

I recently found there was a clojure implementation for .NET and also one for the BEAM Virtual Machine. Has anyone used the latter? Regards

[1] https://github.com/clojure/clojure-clr

Maybe it's not exactly a scheme, but there's Clojure CLR and it's actively maintained: https://github.com/clojure/clojure-clr/wiki

https://github.com/clojure/clojure-clr/commits/master

F# F*

This year I've been attempting Advent of Code in my favourite programming language, F#. This is a beginner(ish) centered post about making incremental changes from the smallest possible solution to something more robust.

I can recommend polyglot notebooks in vs code, so you can mix different languages.Take a look athttps://fsharp.org/ for some project ideas and frameworks.

I have many less followers on Mastodon than in the Birdsite (40 vs 341), yet my activity has generated many more interactions than there. Not only that, among the users who decided to interact with me I counted: a co-discoverer of the Laniakea supercluster, one of the lead developers behind F#, the author of many important books on Java & JVM, plus many others. I'm literally a nobody, but this time there was no algorithm relying on relevance and engament metrics to decide what to present to each one of us.

FP devs differ based on language here. Elm, like F#, tends to encourage "a bunch of functions and types in a file". While Elm supports modules, we don't really care where it came from; they're all pure, all deterministic, the compiler tells us if it works.

The builtin fsharp collections actually are just "immutable", not persistent as you mention. (Ref: https://github.com/fsharp/fsharp/blob/master/src/fsharp/FSharp.Core/map.fs. This is just an AVL tree that returns a copy on mutations: https://github.com/fsharp/fsharp/blob/577d06b9ec7192a6adafefd09ade0ed10b13897d/src/fsharp/FSharp.Core/map.fs#L118)

You can dive into .NET ecosystem by trying F#. It's functional-first language so this should be familiar.

ReScript code is just like F# or OCAML; it doesn’t have a function parse phase like JavaScript, so we have to define our functions and types first before we can use them. That’s fine, but makes explaining the code backwards (meaning you start at the bottom of the file and work your way up), so we’ll start at our lambda handler and explain each part, regardless of where it’s defined.

F# is a JavaScript and .NET language for web, cloud, data-science, apps and more.

Also a programming joke