Content
@
0 reply
0 recast
2 reactions
Gabriel Ayuso
@gabrielayuso.eth
If you're a developer and think OOP is bad. I think you've been radicalized. I don't use OOP much anymore but there's nothing inherently bad with it. You can shoot yourself in the foot and design things poorly using it but you can do the same without OOP. Stop following code influencer advice and just build.
5 replies
8 recasts
108 reactions
Dwayne 'The Jock' Ronson
@dwayne
Why is it said it to be bad?
1 reply
0 recast
0 reaction
Chinmay 🕹️🍿
@chinmay.eth
It's a fundamental mindset that can be used to build layered tech!!
0 reply
0 recast
1 reaction
tani
@tani.eth
OOP has been very fundamental for me in learning about systems If it wasn’t for those principles, I’d never be a good coder I can do functional because I could object well
0 reply
0 recast
1 reaction
Royal
@royalaid.eth
I find OOP on the whole to be a worse experience than working with a more FP codebase. It has its place but I find OOP pushes you to make the wrong kinds of abstractions more often than FP and more importantly, to me at least, I find FP much easier to grasp and work with.
0 reply
0 recast
1 reaction
Vanessa Williams
@fridgebuzz.eth
OOP used poorly is bad. FP used poorly (and excessively) is also bad. Use the right tool for the job, and level up your craft. Pure functions are great for guaranteeing immutability in concurrent code. OOP is good for proper encapsulation, and particularly for DDD. It’s also way easier to achieve extensibility and testability. Use what’s best in each case and don’t take pseudo-religious positions on technologies or techniques. Languages like Scala, Kotlin, and even JavaScript, allow you to have the benefits of both techniques. Java is admittedly klunky now, because it doesn’t handle lambdas well. That’s too bad because otherwise it’s a very useful language, despite all the garbage enterprise code that’s been written with it.
1 reply
0 recast
0 reaction
