[the_af]

> "oh, you just doing it wrong: insert excuse and advise here".

>> Wait til you learn what point-free style is in Haskell! Have fun!

I honestly don't understand what you're trying to say here. Care to elaborate?

As for ORMs: no, other styles of programming don't have this particular problem nor competing abstracting layers approaching this level of chaos. The ORM addresses a specific mismatch problem between relational databases and objects from OOP. This problem is so messily unique that it has been aptly named "The Vietnam of Computer Science": http://blogs.tedneward.com/post/the-vietnam-of-computer-scie...

[dpc_pw]

OOP encourages writing code in "reusable" way of having bunch of objects referencing each other, which throws out of the window the reality of data having an actual form that has to support efficient computation.

This kind of works (to the point) while the data is entirely in memory, but quickly falls appart when it's a bigger data set in external storage.

I am yet to see a OOP project with ORM that have not fall appart in a way I described in these twitter post:

https://twitter.com/dpc_pw/status/1240719977071575040