Scott's Recipes Logo

Thoughts on Claro

This is based on a very cursory initial review of Claro.

  1. As the name of a language, the term claro has a LOT of hits. It wasn’t until I typed in claro language or claro lang that it came up.
  2. Suggestion: Put a link to the github in your CoRecursive profile or describe it as Claro Lang.
  3. Make it very, very clear that this is a JVM language. The JVM is a polarizing technology – example, I won’t even consider anything related to Java or the JVM.
  4. Make the first damn sentence of the readme be what this is good for i.e. claro-lang is a dynamic, type safe language for XYZ.
  5. Figure out what it is actually good for and focus on that. If you want a language to succeed, it needs a purpose. Don’t be elixir and move between different purposes roughly every 18 months (web dev / IOT via nerves / chat / data science).
  6. Put a hello world example in the readme. This is the canonical example of what a language is. Right now you have to dig to find it and it isn’t even there.
  7. Repls go a long way towards making languages approachable and you have one - but you also say it isn’t current. Can’t you take control of your own language’s experience?