5 ms·
> Composing queries programmatically is much easier and less error prone than raw sql when using an ORM. This is only true for the most trivial of use cases th
by jseban 4y ago
> Composing queries programmatically is much easier and less error prone than raw sql when using an ORM.
This is only true for the most trivial of use cases that will not really bring any value to your users. As soon as you get more advanced feature requests, you need the power of the relational model, which is now abstracted away behind a much less powerful interface.
Edit: more advanced, or even just a higher number of orthogonal use cases against the same data.
- scarface74 4y agoHave you used LINQ? LINQ is basically just a slight variant of SQL. All data is related, the only difference between a document type model like Mongo or ElasticSearch is how it stored and retrieved.
- jseban 4y agoI've only been introduced to it, but I did get the impression that LINQ is probably the best SQL abstraction, and that it's much better than Hibernate, which is what I have the most experience with. I think the whole framework situation in general is much better in microsoft land because it's one company that designs the whole ecosystem, and overall experience, and also the people with probably the most experience in software development. I even think VB6 is superior to the standard open source web development stack used today. The only part where MS seems to be behind is version control.
- scarface74 4y agoOh Hibernate sucks. LINQ is built into the language not a bolted on library. How can MS be behind in version control? TFS has had git support for ages and MS owns GitHub.