It seems some fairly major things have been skipped or not updated.
For a while.
Boo support for iphone since version 3.0
2D arrays in UnityScript
Both of which I'd have thought were fairly major accomplishments. And meaningful in many ways.
Those are just two things I know about. Are there more changes that have occurred undocumented?
WAIT BOO IS ON iOS NOW. HOLD ON....NEVERMIND. I DON'T USE IT ANYWAY. :)
Well, they update the Script Reference with every new Version so when 3.3 came out ;) The last extensive update was with 3.0 though.
There are probably some other nuances that are only referenced in one to two places. Unfortunately, I either don't know about them or don't know their hard to find.
Only things that I can think of off the top of my head are:
Generics in js. Add a dot before the <> of any C# generic type.
Function Types. Not much to say. You can pass functions as parameters, and use them for callbacks and such.
Those were both in the Upgrade guide but not everyone knew about them.
Is there a particular reason you're acting proud about not using a language? It's not exactly a virtue to conform, and the only way that language is going to get better is if people start using it.
– ironmagmaEven two languages is a problem. Lots of requests for "No C# please" or "help me translate this javascript." I know some fairly bright guys who avoid things in the "wrong" language. The last thing they need is useful code spread over three languages. It looks like Boo simply comes "for free" with the same Mono engine running C# and UnityScript. The features (lamba-closures, 1st class functions) are traditionally real-time unfriendly.
– Owen-ReynoldsUnityScript isn't translated into Boo, nor is is slower than Boo. UnityScript is written in Boo, but it's converted to CLI code the same way C# and Boo are. (Boo didn't come "for free" either, it had to be specifically written.)
– Eric5h5