Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript JavaScript Loops, Arrays and Objects Tracking Multiple Items with Arrays Removing Items From Arrays

Posted by artdesiatnik
artdesiatnik
2,329 Points

why "length" is a property and not a method like pop or shift?

pop and shift are functions so is length, it does something and there is a code that counts and then returns the value, so why is it property?

2 Answers

Steven Parker
Steven Parker
229,708 Points
Steven Parker
Steven Parker
229,708 Points

:point_right: In general, methods represent actions and properties represent data.

While you're no doubt correct that there is some computation going on behind the scenes, what's probably most significant about length is that it does not affect the state of the object it is applied to. On the other hand, both pop and shift make lasting changes to the object.

So, in keeping with that general principle, it makes sense that length would be implemented as a computed property and not a method.

miikis
miikis
44,957 Points

Good point.

miikis
miikis
44,957 Points
miikis
miikis
44,957 Points

Hi Art,

That's just the design choice that the JavaScript creators made. It makes sense, if you think about it. Functions are these mechanisms that take some optional input, perform some action(s) and optionally return some output. If you only really need the "perform some action(s)" and "return some output" part of this mechanism — if you don't need inputs — then it it would be reasonable to just make this mechanism a read-only property.

But, really, this type of thing is just how JavaScript was designed to be. Sometimes it's arbitrary, other times it's just following idioms that existed in previous languages, like C.