Learn More
Resend Email
4
Wexalian
8y

I'm getting annoyed by the smallest things, like when someone does "test".equals(var) instead of var.equals("test").

It not only reduces readability, it just doesn't look right to me. And I don't think there's a difference in performance between the 2.

undefined

performance

readability

equals

java
Favorite
Ranter
Comments
  • 1
    8y
    Shorter if var can be null
  • 5
    8y
    If var is null, it won't throw a null exception and would still make the comparison. This is preferred by many which avoids code like
    var != null && var.equals("test")
  • 2
    8y
    Well "test".equals(var) is promoted because if var is null it won't cause a null point exception, and it's cleaner looking than a null check then var.equals but besides that i agree i don't like the way it looks either
  • 1
    8y
    @R01101111bert @MAGNUMpt @jckimble I see, I didn't think of that.

    Then again, I think a null-check is nicer than "test".equals(var).
  • 0
    8y
    @Larsg310 null check only clutters the statement, and you have to read extra check before getting to the actual check when inspecting code
  • 0
    8y
    I personally prefer using actual operators, like ==.
  • 1
    8y
    @osmarks while that might work in other languages, it might not work in all e.g. Java.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment