While the language itself doesn't seem very interesting (which is perhaps the point). The idea of building a new language on top of the CLR runtime feels very wise. Instead of a new language suffering from a lack of ecosystem, you get everything else that's already built, even in other (CLR-based) languages. This does leave me wondering what the trade off is. Do you sacrifice any potential language features for CLR compatibility? Or provided you can get it compile, it will run?
Also, are there other language ecosystems with a similar capability?
I have a strong feeling that no new languages will get adopted at all, now that it's important for AI to be proficient in speaking them.
I've been suspecting this myself and its probably the biggest thing I dislike about ai having taken over the proffession.
While the language itself doesn't seem very interesting (which is perhaps the point). The idea of building a new language on top of the CLR runtime feels very wise. Instead of a new language suffering from a lack of ecosystem, you get everything else that's already built, even in other (CLR-based) languages. This does leave me wondering what the trade off is. Do you sacrifice any potential language features for CLR compatibility? Or provided you can get it compile, it will run?
Also, are there other language ecosystems with a similar capability?
The JVM has a ton of languages built on it.
Not really anything here which distinguishes it from c#?