This is a bit of a strange question. But I'm tired of some conversations with my colleague. Can someone PLEASE (I am desperate) give me a technical backup? I try to ignore his harsh language, but finding it is very difficult.
Does this discussion continue? Or is it better to just leave it aside and say something like “no comment”?
As I see it:
- EF more than Linq to Sql
- Our application is slow because our team lacks knowledge and experience, and not because EF is "shitty"
- Perhaps the type of application (huge inheritance and recursive structures) is not used for use with EF
- think twice before saying something, and REMEMBER your opinion (at least for a few minutes).
(3:08:34 PM) TweeZz: it is “fast” until the object is stored in db
(3:08:45 PM) TweeZz: so is it possible that something comes with these objects then?
(3:08:57 PM) TweeZz: and until I press a button, have they separated?
(3:09:21 PM) TweeZz: doubles the time :( (3:09:23 PM) colleague: until you click the button, they have nothing to do with the database, they are just POCO
(3:09:39 PM) TweeZz: k, maybe something is there (3:09:41 PM) colleague: then they will be saved on db and tracked
(3:09:43 PM) TweeZz: change the track (3:09:44 PM) TweeZz : jj
(3:09:55 PM) colleague: but what we know from the very beginning
(3:09:57 PM) colleague: :)
(3:10:03 PM) colleague: it should take some time
(3:10:06 PM) TweeZz: jj was a little surprised at the difference
(3:10:13 PM) colleague: I just hoped that EF wouldn't be soooo shitty :)
(3:10:13 PM) TweeZz: anyway, this too slow
(3:10:20 PM) TweeZz: no comments;)
(3:10:31 PM) colleague: well, I was hoping this would make things smarter
(3:10:45 PM) colleague: it seems worse than linqToSql, but it should be a replacement for him
(3:10:56 PM) colleague: faaaar worse :)
(3:11:15 PM) TweeZz: again, no comment;)
(3:12:19 PM) colleague: myea, I chose it
(3:12:22 PM) colleague: I'm to blame :)
(3:13:01 PM) TweeZz: you can discuss it here;)
(3:13:01 PM) TweeZz: Entity Framework vs LINQ to SQL
(3:13:07 PM) TweeZz: or ask a question
(3:13:12 PM) TweeZz: why EF suck (3:13:12 PM) TweeZz :;)
(3:13:24 PM) colleague: I know the answer is already;]
(3:13:26 PM) colleague: M $: D
(3:13:52 PM) colleague: something is good, so why not give it up and let it do something huge and slow (3:13:54 PM) TweeZz: hehe (3:13:55 PM) colleague: vista: D
(3:17:24 PM) TweeZz: seriously I will post a stackoverflow question
(3:17:52 PM ) TweeZz: how can I tell my colleague that linq for sql does not match the entity infrastructure, and that EF is not "shitty"
(3:18:18 PM) colleague: when did I say that linq to sql matches with EF?
(3:18:30 PM) colleague: I don’t think it’s the same, I never thought that
(3:18:42 PM) colleague: afaik: D
(3:19:16 PM) TweeZz: and then you can discuss your opinion with the community;)
(3:19:34 PM) colleague: thanks;]
(3: 19:40 PM) colleague: you are such help
(3:19:46 PM) TweeZz: how about this? (3:19:47 PM) TweeZz: 3:10:45 PM) colleague: it seems worse to me than linqToSql, but it should be a replacement for it
(3:19:51 PM) TweeZz: I can’t deal with you alone man
(3:19:54 PM) TweeZz: I need a backup
source
share