|
For research purposes only, of course! 
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
On a more serious note, I have noticed some articles that gets a lot of votes and isnt really that outstanding, however the authours seem to quit rather quickly though. 
|
|
|
|
|
Sock puppet article voting... 
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
Oh, no I wasnt talking about my articles
|
|
|
|
|
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
A priest, a rabbi and monk walk into a bar. The bartender looks at them and says, "What is this, a joke?"
|
|
|
|
|
Quote: What is this, a joke?
Apparently not.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
The blonde sitting on the end stool says, "Well, at least it's not on me this time."
Software Zen: delete this;
|
|
|
|
|
|
A beer for the ballerina!
|
|
|
|
|
First of all, thanks very much to everyone who kicked in with thoughts regarding MVC. I'm currently doing some upgrades / installs for VS 2012 since I've been running 2010 so that I can give MVC 4 a go.
Since I'm reevaluating technologies, here's something I just don't get - but perhaps I'm missing something. A year or two ago I played with LINQ. Essentially, it's a nice little chunk of technology to move your db queries into your code.
My approach has traditionally been to use stored procedures, keeping SQL stuff in the database and procedural code / logic in the application. Why on earth would I want to move my queries into C# code?
As long as the params and columns returned don't change, I can make changes all day long in Sql Server and never touch web apps or services. If my db logic is in the code, I have to recompile and deploy the binaries every time I touch something.
I know it's the shiny new thing to play with but other than resume enhancement, I just don't see what value it brings to the table. What am I missing?
|
|
|
|
|
You're thinking of LINQ as "database only" for one thing. LINQ works on other things, like anything that implements or can be cast to a IEnumerable<T> or IQueryable<t>.
LINQ also lets you build a query, piece by piece, defering execution of the query to when you actually use the would-be-returned data.
|
|
|
|
|
You're absolutely right, that was my context. So yes, it would be great to have a structured way of managing data sources that don't live in a relational database. Advantage: LINQ.
How about working with a database, though - any advantages there? That's the part I'm just not seeing.
|
|
|
|
|
On heavily loaded client/server applications, stored procedures can cause major bottlenecks. I was on the fringe of at least two projects where anything more than simple stored procedures were prohibited for this reason (and they had tests to prove it.)
|
|
|
|
|
While I don't doubt what you're saying, the logic escapes me. Either way, you have to hit the database and fetch the data.
What's special about a stored procedure that would make it more of a performance bottleneck than retrieving the same data from the code? Seems like the db is serving up the same amount of bytes either way.
|
|
|
|
|
Because stored procedures take computing time and aren't always trivial. Stored procedures aren't just a few lines of code to do, say, a select or simple update trigger, they can be entire programs which may have little to do with setting/retrieving data, but in manipulating that data. So, who should manipulate the date, the client or the server? (The answer is, of course, it depends.)
|
|
|
|
|
Well, if you're writing entire programs, yeah, I get that. If I want procedural code, I want a procedural language.
But it still sounds to me like if you're just running queries to fetch data or do crud stuff, there's no benefit whatsoever to moving it into the application code. I get the impression people were hot to move that sort of thing to LINQ only because it was new and shiny.
|
|
|
|
|
Christopher Duncan wrote: I get the impression people were hot to move that sort of thing to LINQ only because it was new and shiny.
My impression as well since the alternative to stored procedures is just writing normal queries. A few months ago, I used a tool that refactored some code into LINQ. The end result was only slightly shorter and much more difficult to understand than the original code. Plus, the LINQ code sucked in several more assemblies. I backed out the change.
(My impression is that most things in software development are about being "new and shiny", which is a major headache when you have to maintain the code for someone who constantly got suckered by this.)
|
|
|
|
|
Given that you've been in the game for a long time, I'm glad to hear I'm not the only one who sees this as more resume enhancement / religion than a functional improvement in development.
By the way, just popped over to look at your profile. Do you still fool around with film stuff?
|
|
|
|
|
Christopher Duncan wrote: Do you still fool around with film stuff?
Not much since the 1990s, when I created several interactive videos for edutainment products (and wrote the software.) Lost money, but had a blast. Since then, my biggest project was editing my daughter's wedding video (I should have done a divorce video to bookend that....) I may get back into it one of these days.
|
|
|
|
|
A daughter's wedding is a project in and of itself. I figure the insanity of a major and largely unrehearsed production put on by amateurs is that if you still want to be married by the time it's all done, you should get married. Apparently from your comment that comes with some caveats.
I'm enjoying the video stuff I've been playing with, but monetizing film, or video of any sort for that matter, is about as easy as winning the lottery. I'll do more to support my own creative work as it's just another medium in which to communicate, but it would be nice if there were a way to make a buck at it in the process.
|
|
|
|
|
Joe Woodbury wrote: My impression is that most things in software development are about being "new and shiny"
The band wagon that you see in the distance always looks more shiny than the one that you are on. And since you are not on it and even once you get on, you will have no idea how often it breaks down or why.
|
|
|
|
|
Joe Woodbury wrote: Because stored procedures take computing time and aren't always trivial
Versus for example dragging the entire database across the network, doing calculations on a single client box and then sending the entire database back? (And just to be clear that isn't hyperbole - I actually encountered a system that did that and it would only use one client machine.)
Joe Woodbury wrote: The answer is, of course, it depends
Exactly. Which is far different than claiming that stored procs are always bottlenecks.
|
|
|
|
|
jschell wrote: Exactly. Which is far different than claiming that stored procs are always bottlenecks.
This pisses me off. I NEVER said that stored procedures are always bottlenecks. I said they CAN be bottlenecks and they can be. (Can is a conditional. Unfortunately, this isn't the first time you've distorted what was written, creating a straw man and then attacked the writer. It's getting tiresome. Please learn to read before replying.)
|
|
|
|
|
Joe Woodbury wrote: I NEVER said that stored procedures are always bottlenecks
You certainly did imply that when you also said "where anything more than simple stored procedures were prohibited for this reason ".
You did not qualify that statement nor did you qualify your following statement about the tests used to prove this with the original comment. Your follow on post, and not this one, qualified that you were talking about a specific case with a business model unlikely to ever be applicable to most businesses.
Joe Woodbury wrote: Please learn to read before replying
You said "where anything more than simple stored procedures were prohibited for this reason".
Did you meant that in fact that complex ones were allowed when you said "prohibited"? Did you have some qualification for "simple" which suggested that only really, really complex ones where prohibited or, as I took it, did you mean anything more basic than CRUD?
When you said that there were tests that proved your assertions did you qualify that with the specific business case where it applied? Because I didn't see that when I "read" it. (Nor in this reply either.)
There is of course a difference between qualified and unqualified statements as well as a difference between what one meant and what one wrote.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
