|
I thought that, as a community, we all agreed that steaming pile of movie didn't happen.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
TBH, I think it would be preferable to agree that there have only been two Alien movies.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I'm willing to accept Ressurection as a strange but welcome addition to the library.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
because Windows 10 can boot too quickly for you to miss the beep or pressing F2...
here
diligent hands rule....
|
|
|
|
|
If you miss the time window to hit F2, it's not because the operating system loads "too quickly".
|
|
|
|
|
It's the hardware that is too fast, not the PoC OS that is winio.
Collect your wu mao and your coat, in any order.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
Quote: but I'm having mixed feelings about it
So I do using things like Entity Framework Core or Full
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Why?
Because it makes querying SQL databases easy, making you more productive and making you deliver more in the same amount of time?*
Yeah, those are very good reasons to hate on a software product 
* When you're not expecting lazy-loading when lazy-loading is unsupported
|
|
|
|
|
Did they brainwash update you again?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Hail JavaScript, the one language to rule them all! 
|
|
|
|
|
I don't hate it but also I don't Need it 
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Because you're using another ORM or not using .NET or SQL?
Those are really the only three explanations I have for not needing EF
|
|
|
|
|
Sander Rossel wrote: Those are really the only three explanations I have for not needing EF
with experience far better to swim without water wings, they severely limit style and throttle optimisation.
Sin tack
the any key okay
|
|
|
|
|
I don't really need EF to generate my queries in a certain style... 
When I need optimization EF has certain options, when they aren't enough I can still opt-out of EF in that one instance.
For example, EF can't handle recursive queries, so I write those by hand (and use EF to execute it).
When optimization is a problem I use an SP, but something like context.SomeTable.Where(t => t.Id == id).ToList() can't really be optimized even if I wrote it by hand.
|
|
|
|
|
Quote: Because you're using another ORM or not using .NET or SQL?
a.) another ORM -> No
b.) not using .NET ->No
c.) not using SQL ->No
But I like to have it under my control. Sooner or later I think a lot of users of EF comes to this conclusion.
modified 19-Jan-21 21:04pm.
|
|
|
|
|
You like to write all those SELECT statements by hand time and time again?
When I want to be in control I take control, all those other times I use EF (which is most of the time).
The only optimization I can do to something like context.SomeTable.Where(t => t.Id == id).ToList() is removing the []'s from the generated query...
|
|
|
|
|
Yes
modified 19-Jan-21 21:04pm.
|
|
|
|
|
SELECT TOP 1 Description
FROM TimeWasters
ORDER BY TimeTaken DESC
-----------------------------------------------
Description
-----------------------------------------------
Writing and mapping simple SQL queries by hand.
string topTimeWaster = context.TimeWasters
.OrderByDescending(t => t.TimeTaken)
.Select(t => t.Description)
.First();
Console.WriteLine(topTimeWaster);
Writing and mapping simple SQL queries by hand.
EF is less error prone as it's all strongly typed as well! 
|
|
|
|
|
Perhaps it is only an age phenomenon (I'm pretty old;) ) doing things like this still explicitely by myself.
On the other Hand, if I do it by myself, even it takes me some minutes more, it makes me thinking what I'm doing, which I think is very helpfull.
You are happy with EF, I'm happy with my way. No Need to fight about it
modified 19-Jan-21 21:04pm.
|
|
|
|
|
0x01AA wrote: No Need to fight about it
There is always need to fight with strangers over the internet
*Clears throat to make a snappy comeback...*
Ah well, I'll let you off the hook this time, considering your age and all... 
|
|
|
|
|
Quote: Ah well, I'll let you off the hook this time, considering your age
I'm missing this Thing with one Hand showing one finger 
modified 19-Jan-21 21:04pm.
|
|
|
|
|
No - back in the 90's I wrote a code generator that does all the donkey work for me, is is the standard for the teams and it has been left with at least 10 other organisations over the years. Simple, basic ORM, DAL and code generator that does somewhat more than EF and a whole lot less.
Using that we can generate a solution a faster than EF and it is not a black box, all the devs know the code.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I wrote such a tool for Oracle.
Very simple, primitive, fast and does exactly what it should.
I wouldn't leave it at other organisations though
About a year later I found out another team in our organisation also had such a tool.
However, it assumed everything was a friggin package and that was all it could work with...
I even ran into a very simple scenario that was not supported by the tool. Can't remember what it was, but I remember saying "this is common practice, basics!"
Horrible 
My previous employer also had such a tool... I don't even want to talk about that one! 
|
|
|
|
|
Nice reply! Yes, there are many here who were writing code before the arrival of EF in 2008 and had already created our own tools for doing the grunt work. IMHO, one of the marks of a good (or maybe just lazy) developer is that they have written a code generator. :thumbsup
"Go forth into the source" - Neal Morse
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
