hi guys i'm following your conversation since the ...
# spring
n
hi guys i'm following your conversation since the beginning so here are my 2 cents making classes
final
by default is a good idea we are all lazy programmers so in java, we skip
final
by default because it's easier just as in kotlin, we skip
open
because it's easier however, what does it really achieves? not much in the end that means that it'll need extra effort when you want to subclass (as opposite of needing extra effort when you don't want to subclass) in most use-cases, that's just bikeshedding (https://en.wiktionary.org/wiki/bikeshedding) because it has zero consequences for application developers only for some (not most) frameworks as for the argument of retro-compatibility, that we are now 1.0 guys, do you imagine many use-cases where changing the default would cause a major issue? i don't think major companies have already developed their information system in kotlin sorry for being pragmatic simple smile
👍 1