当集合不断增加和减少时，链表尤其有用。例如，很难想象尝试使用数组实现一个Queue(添加到末尾，从前面删除)—您将花费所有时间向下移动内容。另一方面，对于链表来说，这是微不足道的。

While many of you have touched upon major adv./dis of linked list vs array, most of the comparisons are how one is better/ worse than the other.Eg. you can do random access in array but not possible in linked list and others. However, this is assuming link lists and array are going to be applied in a similar application. However a correct answer should be how link list would be preferred over array and vice-versa in a particular application deployment. Suppose you want to implement a dictionary application, what would you use ? Array : mmm it would allow easy retrieval through binary search and other search algo .. but lets think how link list can be better..Say you want to search "Blob" in dictionary. Would it make sense to have a link list of A->B->C->D---->Z and then each list element also pointing to an array or another list of all words starting with that letter ..

A -> B -> C -> ...Z
|    |    |
|    |    [Cat, Cave]
|    [Banana, Blob]
[Adam, Apple]

Now is the above approach better or a flat array of [Adam,Apple,Banana,Blob,Cat,Cave] ? Would it even be possible with array ? So a major advantage of link list is you can have an element not just pointing to the next element but also to some other link list/array/ heap/ or any other memory location. Array is a one flat contigous memory sliced into blocks size of the element it is going to store.. Link list on the other hand is a chunks of non-contigous memory units (can be any size and can store anything) and pointing to each other the way you want. Similarly lets say you are making a USB drive. Now would you like files to be saved as any array or as a link list ? I think you get the idea what I am pointing to :)

It's easier to store data of different sizes in a linked list. An array assumes every element is exactly the same size. As you mentioned, it's easier for a linked list to grow organically. An array's size needs to be known ahead of time, or re-created when it needs to grow. Shuffling a linked list is just a matter of changing what points to what. Shuffling an array is more complicated and/or takes more memory. As long as your iterations all happen in a "foreach" context, you don't lose any performance in iteration.

链表比数组的维护开销更大，它还需要额外的内存存储，所有这些都是一致的。但是有一些事情是数组做不到的。在很多情况下，假设你想要一个长度为10^9的数组你无法得到它，因为必须有一个连续的内存位置。链表可能是这里的救世主。

假设你想用数据存储多个东西，那么它们可以很容易地扩展到链表中。

STL容器通常在后台有链表实现。

我将添加另一个-列表可以充当纯函数式数据结构。

例如，您可以让完全不同的列表共享相同的结束部分

a = (1 2 3 4, ....)
b = (4 3 2 1 1 2 3 4 ...)
c = (3 4 ...)

例如:

b = 4 -> 3 -> 2 -> 1 -> a
c = a.next.next  

不需要把a指向的数据复制到b和c中。

这就是为什么它们在函数式语言中如此受欢迎的原因，函数式语言使用不可变变量——前置和尾部操作可以自由发生，而无需复制原始数据——当您将数据视为不可变时，这是非常重要的特性。

根据你的语言，可以考虑以下一些缺点和优点:

C编程语言:当使用链表(通常是通过结构指针)时，必须特别注意不要泄漏内存。正如前面提到的，链表很容易洗牌，因为我们所做的只是改变指针，但是我们会记得释放所有的东西吗?

Java: Java具有自动垃圾收集功能，因此内存泄漏不会成为问题，但是对于高级程序员来说，隐藏了链表的实现细节。从列表中间删除节点等方法的过程比该语言的一些用户所期望的要复杂得多。