Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "Functional vs Object-Oriented Programming" | Hashnode

Feed/

Discussion

Victoria Lo

A nerd in books, tea, games and software.

Oct 22, 2020

Functional vs Object-Oriented Programming

In the world of JavaScript, there are typically 2 programming paradigms: Functional and Object-Oriented Programming (OOP). But what exactly are these paradigms, how are they different and when is it best to use them? What's a Programming Paradigm? Pr...

blog.lo-victoria.com2 min read

#javascript #functional-programming #object-oriented-programming #web-development #beginners

Responses4

Markdown supported · ⌘↵ to post

Obum

Full-Stack Blockchain, Mobile, & Web Developer. || Google Developer Expert (GDE) Dart & Flutter.

Oct 30, 2020

Thanks for explaining this very well. Especially for using a simple scenario to demonstrate the difference in paradigm.

You've said knowing when is best to use them takes time and experience.

But please go ahead to specify when it is ideal to use which paradigm or even to use both, so that one will be saved that time and experience and will just implement the best method.

BigDealAgile

See Growth; be growth.

Oct 24, 2020

Thanks so much for this example. Life and solving problems is about making choices. Being open to ideas builds better teams, IMO.

Victoria Lo

A nerd in books, tea, games and software.

Oct 24, 2020

Agree with that opinion! Thanks :)

K M H Mubin

Learning is a mysterious journey

Oct 22, 2020

You explain this very simply, and also the example helps me to understand the concept.

Skay

I love to build cool things on the web...

Oct 22, 2020

This is quiet simple but still has some depth. In fact, I've never seriously thought about OOPS paradigm in JS, since whenever it's OOPS, it's server-side Java that comes to my mind.