Little story about biases in technologies. Before I joined @wavesplatform, I thought that #scala is a very complex, non-obvious and little supported programming language, there is too much magic and you can draw ascii emojis with special characters in your code.

I heard and read a lot about troubles with #scala, and it looked reasonable. But as I dived in it (thanks to @wavesplatform deva and scala courses by @BinaryDistrict), I began to realize that these "troubles" are only my (and people in my bubble) biases.

In fact, scala is like any other popular languages with its own advantages and disadvantages. Same like #Java, #Javascript, #TypeScript, #Python in which I wrote before.

Now when somebody asks me "why Waves is written using Scala and are there any advantages?" I can definitely answer "Yes", there are many.

And the best features of #scala were implemented in RIDE by the WAVES team. That's why RIDE smart contracts language is strong, statically typed, immutable, expression-based, with static types, lazy evaluation, and supports pattern-matching.

Conclusion for me as a software developer is obvious - I must leave my own tech bubble from time to time and try something I don’t like, biases should not influence on choice of tools. I have to listen podcasts and read tech articles, but don’t blindly trust them.

BTW I hope that the maintainer of RIDE language @smagin_waves someday will leave his bubble and realize one important thing about #Javascript - there are cases when it is good enough.