| ▲ | hatefulheart 2 hours ago |
| What optimizations are you making here when at the end of the day performance is dictated by the schema, the query planner and the network? |
|
| ▲ | bot403 2 hours ago | parent | next [-] |
| I read it as "I've optimized the orm to be minimal overhead over raw sql a lot of the time". |
| |
| ▲ | hparadiz 2 hours ago | parent [-] | | I've actually benchmarked the overhead for my ORM against every major PHP orm that exists. https://the-php-bench.technex.us/runs/1 But the speed is irrelevant as long as it's good enough. Notice Laravel's Eloquent at the bottom of the list yet thousands of projects are being built with it regularly. |
|
|
| ▲ | hparadiz 2 hours ago | parent | prev [-] |
| How can I possibly condense 24 years of deep knowledge in one comment for you? The tldr is if you're ever concatenating strings in order to build a query you're just doing what the entire job of orm is but rolling your own and chances are you'll end up with a bunch of bugs in how you handle well.... Everything. |
| |
| ▲ | hatefulheart 2 hours ago | parent [-] | | I think your tone is a bit combative. You can certainly provide the cliff notes but if you want me to believe you’re at working at computational limits whilst talking to me about string concatenation in web dev backend languages I think the burden of proof is on you. | | |
| ▲ | 7bit 2 hours ago | parent [-] | | I don't think OP ever expected you to believe anything. He stated his experience and nothing more | | |
| ▲ | hatefulheart 2 hours ago | parent [-] | | Oh it was just a flex? Ok then! | | |
| ▲ | swasheck an hour ago | parent [-] | | the amount of vitriol my comment generated was unexpected. i was sharing that my experience was the opposite of the comment I was replying to. So many people have read things into it that simply do not make sense to me, including this one. It wasn’t a flex, it was a statement of experience that was simply a different experience than the post I was replying to asserted as truth. As a senior member of the data team, I interact with developer teams regularly and suggest manual handwritten sql for particular performance edge cases, and I met with the response I mentioned. It’s not me not being the team player, it’s the development team using the ORM that has decided that the level of effort to maintain handwritten and ORM sequel is too much for their team to handle |
|
|
|
|
