Programmer Humor

19551 readers

847 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 1 year ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

1226

finally there is a perfect monitor for Java programmers (lemmy.ml)

submitted 1 year ago by likeaduck@programming.dev to c/programmer_humor@programming.dev

116 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] biddy@feddit.nl 1 points 1 year ago (1 children)

As I said, the convention is now x.field() not x.getField()

What language are you comparing against here? x.field[5] is valid Java if field is a public array, but that's not OOP, at least not in a pure sense.

[–] squaresinger@feddit.de 0 points 1 year ago* (last edited 1 year ago)

It's not valid Java for e.g. Lists, Maps, Strings or any programmer-defined classes.

Same with operator overloading.

myVectorA + myVectorB is not valid Java, but it is valid OOP in e.g. Python or C++. And this kind of syntactic sugar reduces verbosity enourmously, while still being OOP.

If you have ever worked in e.g. Python, Groovie or Kotlin you notice quickly how non-verbose OOP can be.

It seriously is just Java.

And Javas insistance on having you wrap non-OOP things in fake OOP constructs (e.g. static methods, which are just functions in modules, but you have to uselessly abuse classes as modules) isn't helping either.