Instance vs Prototype Methods for AngularJS Controllers in Typescript

Question

If I don't intend to inherit my controller class, is there any difference between defining an AngularJS Controller's methods as prototype methods over instance methods?

Coming from a C# background, I'm more comfortable with defining prototype methods. I also like keeping the constructor short.

However, most examples I see for AngularJS define methods at the instance level.

module Test {
    angular
        .module("app")
        .controller("controller",
        ["$scope", MyController]);

    export class MyController {

        public Function1: () => {}

        constructor(private $scope: IMyScope) {
            //instance
            this.Function1() = () => {
                alert("Hello 1!");
            }
        }
    }

    //prototype
    public Function2(): void {
        alert("Hello 2!");
    }

}

basarat · Accepted Answer · 2015-01-05 12:12:43Z

1

If I don't intend to inherit my controller class, is there any difference between defining an AngularJS Controller's methods as prototype methods over instance methods?

Instance methods come with a performance impact. Other than that it's perfectly fine to use them. I just use prototype members.

This video explains why you might want to use instance methods : https://m.youtube.com/watch?v=tvocUcbCupA (mainly to capture this)

answered Jan 5, 2015 at 12:12

basarat

278k61 gold badges475 silver badges528 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Instance vs Prototype Methods for AngularJS Controllers in Typescript

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related