|
|
|
|
|
by Chlorus
2113 days ago
|
|
> "this ORM is just bad, next time we will use a different one" ...pretty sure there are competing abstraction layers to working with DBs other programming paradigms. > OOP works on low complexity, small projects, but quickly falls apart at certain point,
> More experienced people figured out some way around OOP to make it more robust, I thought it fell apart? > "oh, you just doing it wrong: insert excuse and advise here". Wait til you learn what point-free style is in Haskell! Have fun! > People who really though it through, and tried different approaches are the ones that hate it and are vocal about it. So if you happen to like OOP, you just haven't thought it through. Thanks for the constructive comment! |
|
>> 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...