Posted over 10 years ago. Visible to the public. Linked content.

Otaku, Cedric's weblog: Why Java doesn't need operator overloading (and very few languages do, really)

The number of operators that you can overload is very small and each of them is attached to very specific semantics that makes little sense outside the realm of scalars and of a few other specialized mathematical concepts (e.g. matrices).

Growing Rails Applications in Practice
Check out our new e-book:
Learn to structure large Ruby on Rails codebases with the tools you already know and love.

Owner of this card:

Avatar
Lexy
Last edit:
about 9 years ago
Keywords:
language-design
About this deck:
We are makandra and do test-driven, agile Ruby on Rails software development.
License for source code
Posted by Lexy to makandra dev
This website uses cookies to improve usability and analyze traffic.
Accept or learn more