The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Daily, yes. You just have to be very careful with how you write the queries and constantly inspect what Linq-to-SQL projects into actual SQL. Sometimes Linq is so clever that it project terrible and slow queries but in most cases you can fix it by "rewording" your Linq queries.
I believe Entity Framework has the same projection problem.
Nope. Since I write mainly in VB I find the Linq syntax to be very cumbersome and hard to use. When I write in C# I'm far more likely to use Linq simply because the lambda syntax is far easier to read and use. In neither case do I use Linq -> SQL
Tried it for a project but quickly had to abandon it. Found it too rigid. If you try using against a many databases. When one database adds a field, it completely breaks querying the table.
Though I enjoyed learning about CROSS APPLY from examining it but discovered that it hits a cap where it performs better than anything else in a limited use environment, but once you pass a threshold it takes down systems.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle