6 ms·
No ORM. Sucks having to learn a new ORM every project. Even worse when you need to do something in a new ORM one step more advance than the tutorials show you.
by postalrat 4y ago
No ORM. Sucks having to learn a new ORM every project.
Even worse when you need to do something in a new ORM one step more advance than the tutorials show you.
- simplotek 4y ago> No ORM. Sucks having to learn a new ORM every project. I don't quite follow your logic. ORMs provide a lot of critical features for free right out of the box which take a lot of time and effort to roll out by hand. Database migrations are perhaps the hardest to get right, for example. Why do you believe that the trivial job of onboarding onto a ORM is too much to handle, but manually rolling out and maintaining and debugging hand-written code is somehow an acceptable loss of productivity?
- javcasas 4y agoLearning the ORM is easy. On the other hand, learning the ORM bugs...
- postalrat 4y agoIt's never a trivial job. And in my experience it's rarely a single ORM. You will have one for the js code, on for the .net code, one for php, on for ruby, etc, etc. And your developers are going to be sitting read docs for hours to do many things beyond a trivial query.