Why are arrays so shitty to work with?

Why are arrays so shitty to work with?

Attached: Cs3KTUEUsAAgQPm.jpg large.jpg (500x449, 19K)

it's dont

Becaus vectors are chad

They arent

Even if they were shitty, they're what your processor was designed to crunch as quickly as possible. Deal with it.

What else would you prefer? A linked list?

>the virgin linked list
>constant time insert, but only in theory
>keeps missing the cache
>only gets use by lazy C programmers and sedentary memory

>the Chad dynamic array
>has never seen a cache miss in his life
>copies himself entirely on insertion, somehow still faster
>travels all the time, still local everywhere he goes

Attached: jc_denton_in_da_fresh.jpg (437x665, 147K)

because you are using shit languages like C/C++ instead of fortran or R or numpy

>the Chad dynamic array
>can't be lock-free

>arrays
>shitty to work with

let me guess: you were dropped on your head as a child? arrays are the easiest data structure to work with. life would be so easy if i could solve ever problem using the vector class

>has to redesign his innards to please threads
>not a virgin
Chad uses spin locks and doesn't give a fuck.

>dynamic linked array
*blocks your path*

>Why are arrays so shitty to work with?
What problems are you having user and what are you trying to do?

Attached: 1__spurdo-animooted.gif (458x438, 103K)

Now implement a cactus stack.

It's because you use a shitty language. Use Prolog

Its a primitive type.

If you want to hold a lot of things and actually have functions to use, try a collection class like List. In fact, I laugh when people choose primitive arrays over 'proper' data types simply because they dont know any better

If something requires non-negative IQ it doesn't automatically make it difficult.

What are you storing in that array, OP? Is it some sick shit?

Attached: westworld.jpg (116x117, 16K)

array[index].value

whats so hard about this?

it's offset from the first element

? In what unholy abomination of a language do you retrieve an array entry with "array[index].value"?
Even java is more sane than this.

Wat?
array[0] is the first, array[1] the second entry and so on. It's not hard when you can do math on elementary school level.

>array[index].value

Attached: 1527107777803.gif (295x221, 613K)

Best thing for tards like you to help understand arrays and indexing is a deck of cards. Simulate that shit in your hand.

think about it, you'll get it eventually