Comments by "Christian Baune" (@programaths) on "Fireship"
channel.
-
At some point, they will rename Kotlin to Java and get done with it ^^
Also, I have yet to meet one single programmer who understands OOP.
OOP is wrong because it needs to be easier to understand.
When I was a QAM, all dubious code attempted to leverage OOP, leading to tight coupling, lava code, action at a distance, and side channels.
And when we talked about it, I had to ask, "Why do you need to know what it was called? Why do you need to know what it will do? Why can't you rearrange those unrelated statements?"
With Kotlin, you can easily create data classes, have first-order functions, have extension functions, and have delegation facilities.
On top of that, there is a misconception (shown in the video) that objects eat up memory. The JVM is excellent for dealing with short-lived objects! And with JIT, code that is well written will end up reasonably optimized. By avoiding creating too many objects and methods, people prevent the JVM from doing its work. Sometimes, pooling is just combatting the JVM.
And the issue lies there; one has to know a bit about the JVM.
2
-
1
-
1