I think it's a case of deciding to focus the innovation budget somewhere else. Claro on the surface level looks a lot like Go, and it's probably intentional. Cr

I think it's a case of deciding to focus the innovation budget somewhere else. Claro on the surface level looks a lot like Go, and it's probably intentional. Crafting an unique syntax, making sure it's efficiently parseable, and nice to use is a whole lot of effort, and the solutions we have today in this space are basically fine. Claro seems to focus its efforts elsewhere - the main innovation seems to be its graph-based multithreaded work scheduling which is a novel concept, and has major implications for program organization, just not syntax.