The Current State of Clojure's Machine Learning Ecosystem

• clerk

  22 1,697 8.5 Clojure

  ⚡️ Moldable Live Programming for Clojure

  

Something I really like in the Clojure data science stack that isn't mentioned is Clerk* — an interesting take on notebooks. I think it's a good gateway into Clojure for those coming from a Python or R background.

*https://clerk.vision/

• gleam

  95 15,033 9.9 Rust

  ⭐️ A friendly language for building type-safe, scalable systems!

  

While I love Clojure, I have to agree about tooling. I recently started using Gleam* and was impressed at how easy it was to get up and running with the CLI tool. I think this is an important part of getting people to adopt a language.

* https://gleam.run/

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• EFCore.FSharp

  4 228 3.4 F#

  Adds F# design-time support to EF Core

  

• Smile

  9 5,924 9.8 Java

  Statistical Machine Intelligence & Learning Engine

> I don't think it's right to recommend that new users move away from the package because of licensing issues

I was going to chime in to agree but then I saw how this was done - a completely innocuous looking commit:

https://github.com/haifengl/smile/commit/6f22097b233a3436519...

And literally no mention in the release notes:

https://github.com/haifengl/smile/releases/tag/v3.0.0

I think if you are going to change license especially in a way that makes it less permissive you need to be super open and clear about both the fact you are doing it and your reasons for that. This is done so silently as to look like it is intentionally trying to mislead and trick people.

So maybe I wouldn't say to move away because of the specific license, but it's legitimate to avoid something when it's so clearly driven by a single entity and that entity acts in a way that isn't trustworthy.

Suggest a related project