Why do people think that data structures are interchangeable??
Each fucking one answers a set of constraints!!! Yes, you can still use it, but let's be clear: even if you can screw with a shovel, you should still use a screwdriver!!! Functional constraints generate technical ones, not the other way around!!!!

And for fucks sake stop searching "EASY", and start chasing SIMPLE!!!!

They probably used PHP before.

The KISS principle.

Understand it. Use it. Stop being a wiseass.

I heard HashMaps are fast, so I make everything a hashmap. That's how you make fast code guys!

@Oktokolo if only! It'll be easy to solve.

How many JAVA use studiply hibernate because it's easy (with a stupid, disgusting data architecture)? Too many to count.

Python lets use NumPy without understanding what the fuck it does in reality? It doesn't make sense and it way too costly? Still answering under 1s so don't "over-engineer it".

Elastic search, because their MongoDB collections as fucking disgusting and not usable for what should be a basic filtering request.

How many relation tables in SQL, just cause... You know it's all decoupled and what can be 3 tables creates, is now a beautiful schema filling an A2 page...

We don't have communication problems BUT we need to do the daily because it can't work without it! And if you think it's useless, it's not because you already solved the problem the daily tries to solve, but because you're doing it wrong.

So much stupidity!!!!

@jotamontecino
Java actually has a pretty complete collection of data structures in its standard library. Not sure i would ever consider the default serialization framework though (but it may have evolved a lot since i last touched Java)...
And it is hard to make anything slower by using NumPy (but you can make anything slow by chosing the wrong algorithm of course).

But relational database design - yes, that is hard for most people. You easily end up with duplicate (and therefore inconsistent) columns or an over-normalized schema where every string is a stored in a strings table...
If RDF stores where some orders of magnitude faster, nobody would still use relational databases. But sadly they aren't.
And it is pretty easy to make queries painstakingly slow by joining a couple of tables on non-indexed fields.
Relational database design and maintenance is its own field of expertise for a reason. Add stored procedures and nobody but you will ever be able to maintain that project...