@akop I am so glad about languages like Kotlin which offer non-nullable types. Exactly that will get unnecessary and also survive refactorings. #kotlin
Java’s records are a bit like Go’s interfaces. You think you’d be using them for everything, while in reality, they’re good for like 2-3 cases. Indeed, in those 2-3 cases, they’re really saving the day, but using them everywhere “just because” will result in an incomprehensible mess.
I have just learned that "#Java Bean" has two completely different and incompatible definitions.
One is a dumb, badly designed data object with getters and setters.
The other is... a service object managed by the Spring framework IoC container.
Holy hell. This is 10x worse than #Laravel "facades."
Am I wrong here? This is what I'm finding from online tutorials. Is there more nuance that is not coming through, because for now I just hate #Spring even more.