Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7633925
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T07:01:30+00:00 2026-05-31T07:01:30+00:00

As far as I understand, Prototypal inheritance and closure are two incompatible ways for

  • 0

As far as I understand,Prototypal inheritance and closure are two incompatible ways for creating objects.

  • With prototypes, all the instances share the same function
  • With closures, each instance has its own function (with its specific closure)

By creating object using clojure, I am referring to the following pattern:

    function createPerson(p){
           return { 
               getName: function() { return p;} 
           };
    }

When in writing a Javascript application, prototype is a better choice than closure for creating objects? I am not looking for general explanations about the advantages of prototypal inheritance. Instead, I would like to see a real-life web development scenario where prototype inheritance is really useful.

The only useful case I can think about is for augmenting basic types.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-31T07:01:31+00:00Added an answer on May 31, 2026 at 7:01 am

    In your new example you don’t “create a person”. Instead, you return a plain js object.
    Again, is not about closure versus protytpe, because I can also have:

     function createPerson(p){
           return { 
               name : p,
               getName: function() { return this.name } 
           };
    }
    

    That doesn’t take advantages of a closure, but use the same approach to create an instance of an object. As you see, using closure again has nothing to do with object creation, can be used – or not – together, despite if you use prototype or not:

    function Person(name) {
        this.getName = this.getName.bind(name);  
    }
    
    Person.prototype.getName = function(name) {
        return name;
    }
    

    I generally avoid that, but you can have it. Also:

    function Person(name) {
        this.getName = function() { return name };
    }
    

    So, if your question is “why I should create an object in this way instead of a plain object” – that has nothing to do with closures – the answer is “because then you take advantage of the inheritance”:

    function Mutant(name) {
        Person.call(this, name);
    }
    
    Mutant.prototype = Object.create(Person.prototype);
    
    var cyclops = new Mutant("Scott Summers");
    
    alert(cyclops instanceof Person) // true
    
    alert(cyclops instanceof Mutant) // true
    
    alert(cyclops instanceof Object) // true
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

All, As far as I understand ASP.NET MVC is the framework that implements the
As far as I understand, if I want to get my database under source
As far as I understand, binding to a var in ActionScript is carried out
As far as I understand, https is http plus SSL/TLS. What do I need
As far as I understand, the onchange event of a text input element is
As far as I understand the serial port so far, transferring data is done
As far as I understand WebRequest.PreAuthenticate is almost always good. If I enable it
As far as I understand the branch-on-sign is the name of some kind of
Here's as far as I understand it: Client & Server make connection Client sends
Java's Executor is (as far as I understand it) an abstraction over the ThreadPool

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.