Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

Comment Re:Rats. (Score 1) 417

If they coded in C#, sure, I'd try to convince them. But hard to cost justify dropping an existing business codebase that uses a particular language just to pick up a better database access library.

But if you're an up and coming business, this is the way to do it.

Comment Re:Rats. (Score 2) 417

> hey willingly put their heads in the guillotine by adopting YA3GL (C#/.NET) that gives no advantages unless you want to do things the Microsoft way

Gives no advantages? Bullshit. Have you ever worked with the Entity Framework under C#? Way beyond the best way of working with data I've ever encountered. I am able to crank out solid data-intensive code in 1/10 the time it would take me with NHibernate or Java with Hibernate, let alone older attempts at making data a first class citizen in the language. MVC 3 or 4 with Entity Framework 4 or 5 makes you able to crank out stuff in a few weeks that used to take a year with all the boilerplate crapCode you use to have to write. (Assuming you start with a good architecture design)

Comment Re:Why are people still using this? (Score 1) 367

I haven't used EF against anything but MSSQL, so haven't ran into what you've experienced. Although I'd be hesitant to use it with something else, there's no way you'd get the deep integration with a third-party database server. But for solutions based on MSSQL, there's nothing better I've seen in any world.

3. Usually when I run into issues like that, I'm doing something stupid. There's a few cases (Like working with Full Text Search) where I drop back and use a stored proc, but 99% of what I do, EF and Linq has not let me down.
5. Check your project configuration, you can set it to push out the same version of EF that you used for development.
6. Who the hell is modifying the database schema in production without going through proper QA? That's a management issue, not an EF issue.
7. See #5

Comment Re:Why are people still using this? (Score 4, Interesting) 367

Have you worked with C# under the .NET 4.x framework now that they've added Entity Framework to it?

It is so much more efficient that any other data access abstraction I've ever seen. It even makes Hibernate/NHibernate look like a lame hack.

I am able to do extremely complex things with 10% of the amount of code I used to have to write.

Microsoft might be making a LOT of mistakes lately, but Entity Framework is not one of them. I don't know if I'll ever have the patience to use another language again - C# with Entity Framework is that much better.

Comment Re:Field dependent requirement (Score 1) 1086

Wow, I really liked that link about Lambda Calculus! While I have used Lambdas and Anonymous Methods heavily in C#, I never knew there was a formal science devoted to it.

It was cool for me, as both a GED student and a lead developer, to read something on an advanced math subject and fully understand it. However, for the same reason I am a relatively advanced programmer (Business, nothing cool like videogames) I would never have learned it from that article - what an atrocious syntax! Why is so hard to describe something so easy?

Slashdot Top Deals

Those who can, do; those who can't, write. Those who can't write work for the Bell Labs Record.

Working...