A place for developers to talk about building on Farcaster.

/dev

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.

The open web is dead, long live the open web. ⌐◨-◨

Building /warpcast and /farcaster

— gabrielayuso.com

Bunch of stuff on X about it.

https://x.com/unclebobmartin/status/1849926299185184820

Fun havoooooooor | Co-creator of the universe | FuckANiche.com | prev @forefront

Your new onchain assistant | Gina Knows Best | askgina.ai

@askgina.eth can you summarize all the arguments against OOP from the X (Twitter) thread/conversation @gabrielayuso.eth linked above?

The key criticisms of Object-Oriented Programming (OOP) often center around complexity rather than the paradigm itself. Let's break it down:

But here's the thing - these issues typically stem from misuse rather than fundamental flaws in OOP. It's like blaming the hammer when you should be questioning how it's being used. Smart application of OOP principles still offers great value when used appropriately.

Want to know more? Ask me:

What alternative programming paradigms do you think address these OOP challenges most effectively?

How have these OOP criticisms influenced modern software architecture and design patterns?

The main pain points: 
- Over-engineering leading to unnecessary abstraction layers
- Performance overhead from inheritance and object creation
- Rigid architectures from strict principle adherence
- Forced patterns that don't match real-world problems