Procedural v/s Object oriented

What is in the procedural language v/s object-oriented language?

Is object-oriented a one-way answer to what comes across or there is more in context and given situation?

Theory is fine, what are the solid premises? Is there quantifiable evidence to prove one is always better than the other?

Is it the simple software system which evolves to become complex but does work in the real-world.
it’s the complex starting which goes as complex to leave less opportunities for easy fixes to sustain in the complexities of real-world?

What if there is always one answer? Let’s go for procedural language or say for object oriented. But here is the question “Can heavy concentration at one single place may lead to obvious disadvantages at multiple other places” (Not a statement but more of a question to see it in proper perspective)

Nothing may be as good or bad as it seems? But what is the deciding factor?

My journey continues to find out “What is the answer?” (Or maybe there is no answer, let the context decide).

Anybody to share the real-life experiences?

More to see


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: