4 ms·
While we need more context as to where this handwritten SQL is going (into a codebase [with parameterization ] to get code reviewed / PRed / compiled , vs. bein
by myu701 7y ago
While we need more context as to where this handwritten SQL is going (into a codebase [with parameterization ] to get code reviewed / PRed / compiled , vs. being typed in by a user to some textbox etc. ) to more specifically comment, I have a tendency to avoid ORMs at all costs since (dogma ahead!) they are never worth it long term. In very specific circumstances, they can make translating domain types into database access feel simpler, but their indirect costs almost always outweigh their use in my (limited, granted) experience.
- potta_coffee 7y agoORMs are omnipresent in web development, but I've seen this point of view that they're harmful being kicked around. I'm interested in knowing the tradeoffs, and also what it looks like to build applications without ORMs. What kind of stack are you using? Any information about the pros/cons?
- it 7y agoWe're using Typescript with typeorm and a Postgres backend. The backend speaks graphql to a frontend written with Typescript and React. Pro: Lots of people seem to be doing it this way, so there's plenty of info out there and it's probably easier to hire more people to work on it. Cons: It's easy to make mistakes about authorization and even just wiring things up since typescript's type system doesn't catch some bugs that it seems like it should catch. It's tedious compared to postgrest, at least from what I've seen so far.
- potta_coffee 7y agoThanks. How do you like GraphQL?
- it 7y agoI like its RPCishness, but it also seems to require a lot of repetitive coding.