I think the point they were trying to make is for using ORM for everything until you need a query complex enough or performant enough to drop back to a raw SQL layer.
That's the pattern I've seen the most with ORM setups these days. That or dropping performance heavy sql into stored procedures but in the end it's all a matrix of ease of use/maintainability in some scenarios vs full control and performance tuning and what makes sense for that use case.
Then please forgive I was triggered on their introductory expression "Raw SQL is great for simple queries, (...)"
I understand your point but I'm not sure it's efficiency to use an ORM that abstract the easy stuff away from the programmer but rely on expert level knowledge to solve what remain. Because at this point the developer that build everything with an ORM will either:
- Face complexs SQL query that he'll have to build from the ground up by summoning expert SQL skills they probably haven't use for a while
- Seek external help from an SQL expert than doesn't know how the system was build in the first place*
If you know you'll need database specific SQL optimizations on complex query in the end, I guess using SQL everywhere could also make sense. Same language and code logic from simple to complex query and a complexity gradient in between.
*I guess same point could be made about vibe coding actually.
Not OP but as I understand it they say RAW sql works great for the very basic stuff. But when it becomes a bit more complicated it is easier to mess up and an ORM is preferred. Then you have the very complex queries where ORM just become more difficult or creates bad performance. Then you have to use raw sql.
So basically raw sql or orm does not matter for very simple queries. For more standard queries with lots of joins and where clauses ORM is better to not deal with complex sql. Then you reach a point where you must use raw sql because the alternative is worse.
In most apps most queries is probably in that middle chunk.
Hyundai had a not so great reputation in the early 2000s in the US. In recent years however this opinion seems to have shifted.
Been driving an Ioniq 5 2023 for a couple months now with no phantom/emergency braking issues. I'm not in love with the performance of the lane keep without being on an HDA2 marked highway. I have to fight it just enough for it to not be useful on certain well marked backroads.
Considering tossing in a Comma 3 to give no-hands driver assist a shot.
Hyundai has been having engine failures, would not recommend as experienced spontaneous engine failure on a less than year old car. Check consumer reports or source below.
“In 2020, NHTSA announced civil penalties for the companies—totaling $210 million—for not recalling vehicles in a timely manner. In 2021, a whistleblower who provided NHTSA with information that led to those penalties was awarded $24 million, the agency’s first-ever whistleblower award.”
Hyundai had terrible engine and transmission problems in the 2010s. A local dealer was offering 20 year warranties to get them off the lot. There was a Reddit post of a 300k+ Kia that had gone through something like 7 engines and 4 transmissions. They basically 4 new cars worth of engine and transmission parts.
They have great styling that’s comparable to German cars. I wish the US automakers could take some hints. From what I’ve heard the Genesis lineup is very luxurious.
Comma 3 is s the best, to be honest. Due to CAN-FD on Ioniq 5 the setup is a little bit more complex, but this is the best experience, though they are still working on their own AEB implementation.
The privately owned org that I started with recently has new comers at a pretty constant 30% annual bonus. Tied to how well the company did but upon conversation with veteran staff, no issues with management paying out or percentage drops in the last 15 years.
They aren't a perfect company by any means, but they seem to be decent from current observations.
They decided to modify a number of core functions to work the same way as their old terminal system instead of the default ERP process. Now our job for the next couple years is decoupling the custom add-ons so we can safely update to a modern ERP system.
Blazor Server downloads a small js script (SignalR) to the client on connection. All user events are sent back to the server through SignalR, then DOM changes are sent back to the client based off of user input.
I use it at work for internal intranet web apps so it's pretty handy for our use case.
That's the pattern I've seen the most with ORM setups these days. That or dropping performance heavy sql into stored procedures but in the end it's all a matrix of ease of use/maintainability in some scenarios vs full control and performance tuning and what makes sense for that use case.
reply