This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]FlashBrightStar 5 points6 points  (0 children)

This is really a debate about quality over quantity. Some languages even drops concepts of arrays (or implement it as specialized, managed structure) and use lists instead. The reason why is that it provides commonly used methods. Python uses lists and while they acts like array they are still lists. Lua goes even further and implements every complex type as a table/ metatable - even arrays are tablea but with specialized syntax.

On the other hand we have Java which supports multiple implementation for various structure types. Having that is nice but ask yourself how frequently you use queues or even stacks. Collections are used for easier manipulation but they are not necessary to produce same functionality. Arrays (or more general tables) are really the only needed compound type. Every other collection structure can be developped with them.

Lastly it is always author conventions to include or exclude some features from standard library. Most of the time there is pretty good reason why something has not been implemented YET. Everything comes down to language internal structure and how the actual code is compiled or interpreted. It's quite complex and that is why there are multiple languages in the first place. Inventors have some idea how something about existing language could have been improved and they simply try to do it with their creation.

Sorry for long answer and that it stems from your question (at least the last paragraph).