React is actually pretty nice. Im probs saying this because it handles oop stuff like java would and im extremely fucking biased, but its a lot more enjoyable than angular.

Also if you get the joke in this pic (found in the react tutorial), hats off to you, it made me lol

What’s the object-oriented way to get wealthy?

Inheritance

it's time to review your concepts!!! lol

Emojicode is a full OOP language. Should I build my startup on it?

last semester i was working as assistant professor teaching Basic OOP Subject. and my girl happens to be enlisted as my student. One day she was late for my class and get in without a permission. so i ask her
Me : Why don't you knock the door?
Her : Why should i ?
Me : did i give you my permission ?
Her : Public class doesn't need permission. our class is not Private.

oh my god i'm so in love with her

"I don't see women as objects, each woman is in a class of their own! HAHAHAHAHAHAHAHA"

- People who have no fucking clue how OOP works

Objects are instantiations of classes, you poor, retarded bastards. You saw those two words while skimming your 1st year college textbook, made this joke, promptly changed to some useless English degree because you cried after your "hello world" program didn't run, and never looked back to see the damage you had done.

I know the joke is the word play but word play word play puns are retarded anyways. Everything about this pun is awful.

The easy way

Decided to spend my weekend on a little side project that I thought I could finish quickly.

Not only does my code not work, but what I wrote is so horrible that I'm honestly ashamed. Its like the despicable porn that you sometimes end up watching and the horror of realizing what the hell you just watched after you finish - I thought my code was good, but really, it was trash.

Before I started writing I though to myself, "I'll finish this project and then I'll upload it to my Github to expand my repository", but now I cringe at the thought of someone else reviewing this pile of shit I call my code.

It's 2 am here in Israel. I know I should go to sleep, but I'll just stare at the ceiling, feeling unproductive because everything I did today is literally worthless.

How the fuck do I justify this shit to myself? Calling this a "learning experience" feels like a fucking joke.

Honestly, I don't know why I chose Python to do OOP when Kotlin would have served me much better.

But, there's always tomorrow, isn't there?

Recently I had the "pleasure" to participate in a recruitment process for a web developer internship position.

First of all, a nice lady calls me to confirm everything and sets up a meeting. She mentions about a qualification test and gives me several technologies like python, c#. I was confused but we explained everything and she knew I was not interested in these technologies since I didn't apply for python or c# dev.

Later on I go to their company building to take the test. I get the test, I overview all tasks - 80% of the test was composed of OOP and C#. OOP - this I can understand but fucking C#? Seriously wtf? I wrote the test the way I was able to do it and at the end the guy says it was deliberate to put other technologies so that he could check how would we find ourselves in a situation like this.

Honestly, I felt like the whole process was a big joke for them. I wasted time going there just to see that I'm taking the test that includes the things posted in the job offer only in 20%.

Fuck them.

Sydochen has posted a rant where he is nt really sure why people hate Java, and I decided to publicly post my explanation of this phenomenon, please, from my point of view.
So there is this quite large domain, on which one or two academical studies are built, such as business informatics and applied system engineering which I find extremely interesting and fun, that is called, ironically, SAD. And then there are videos on youtube, by programmers who just can't settle the fuck down. Those videos I am talking about are rants about OOP in general, which, as we all know, is a huge part of studies in the aforementioned domain. What these people are even talking about?
Absolutely obvious, there is no sense in making a software in a linear pattern. Since Bikelsoft has conveniently patched consumers up with GUI based software, the core concept of which is EDP (event driven programming or alternatively, at least OS events queue-ing), the completely functional, linear approach in such environment does not make much sense in terms of the maintainability of the software. Uhm, raise your hand if you ever tried to linearly build a complex GUI system in a single function call on GTK, which does allow you to disregard any responsibility separation pattern of SAD, such as long loved MVC...
Additionally, OOP is mandatory in business because it does allow us to mount abstraction levels and encapsulate actual dataflow behind them, which, of course, lowers the costs of the development.
What happy programmers are talking about usually is the complexity of the task of doing the OOP right in the sense of an overflow of straight composition classes (that do nothing but forward data from lower to upper abstraction levels and vice versa) and the situation of responsibility chain break (this is when a class from lower level directly!! notifies a class of a higher level about something ignoring the fact that there is a chain of other classes between them). And that's it. These guys also do vouch for functional programming, and it's a completely different argument, and there is no reason not to do it in algorithmical, implementational part of the project, of course, but yeah...
So where does Java kick in you think?
Well, guess what language popularized programming in general and OOP in particular. Java is doing a lot of things in a modern way. Of course, if it's 1995 outside *lenny face*. Yeah, fuck AOT, fuck memory management responsibility, all to the maximum towards solving the real applicative tasks.
Have you ever tried to learn to apply Text Watchers in Android with Java? Then you know about inline overloading and inline abstract class implementation. This is not right. This reduces readability and reusability.
Have you ever used Volley on Android? Newbies to Android programming surely should have. Quite verbose boilerplate in google docs, huh?
Have you seen intents? The Android API is, little said, messy with all the support libs and Context class ancestors. Remember how many times the language has helped you to properly orient in all of this hierarchy, when overloading method declaration requires you to use 2 lines instead of 1. Too verbose, too hesitant, distracting - that's what the lang and the api is. Fucking toString() is hilarious. Reference comparison is unintuitive. Obviously poor practices are not banned. Ancient tools. Import hell. Slow evolution.
C# has ripped Java off like an utter cunt, yet it's a piece of cake to maintain a solid patternization and structure, and keep your code clean and readable. Yet, Cs6 already was okay featuring optionally nullable fields and safe optional dereferencing, while we get finally get lambda expressions in J8, in 20-fucking-14.
Java did good back then, but when we joke about dumb indian developers, they are coding it in Java. So yeah.
To sum up, it's easy to make code unreadable with Java, and Java is a tool with which developers usually disregard the patterns of SAD.