ORM is not bad, in fact no framework or technology is bad in anyway, the only thing bad is trying to do everything in ORM is bad. Large application has many components written in different technologies and all components communicates efficiently to make one large system.
ORM can be unit tested, trying to unit test RDBMS is pain. You can compose queries in ORM easily, composing and debugging queries in SQL is painful, its not impossible.
First iteration of logic is easy to write in ORM, and then once it is mature, it is easy to translate to SQL. Entity Framework Core generates pretty readable queries, same can be moved to SQL easily.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
ORM is not bad, in fact no framework or technology is bad in anyway, the only thing bad is trying to do everything in ORM is bad. Large application has many components written in different technologies and all components communicates efficiently to make one large system.
ORM can be unit tested, trying to unit test RDBMS is pain. You can compose queries in ORM easily, composing and debugging queries in SQL is painful, its not impossible.
First iteration of logic is easy to write in ORM, and then once it is mature, it is easy to translate to SQL. Entity Framework Core generates pretty readable queries, same can be moved to SQL easily.