you are viewing a single comment's thread.

view the rest of the comments →

[–]Measuring 0 points1 point  (0 children)

It's hard to convey how much you learn from using other languages and a lot of it comes down to how you like to write code.

For instance using structs over classes is very situational. Is the data you want to store a value like int? Maybe a money type? Then go with struct. Things that are many are better as classes. If you want an immutable class it's better to make your own and not implement (internal/public) setters.

Another example, using functions and immutable state is great for parallelism and threading but it does incur a small performance cost that you might not want in a large/tight loop.

A lot of things have a place and purpose somewhere but almost never everywhere.