1) Makes no sense whatsoever; stored procedures are typically going to be much faster than the equivalent mix of application-level code written in a scripting language that needs to communicate with a database and is likely vastly slower than PL/pgSQL or PL/SQL. The hardware licensing costs having nothing to do with stored procedures and apply just as much to anything else (there's free as an beer options and costly proprietary ones in either case).
2) This is not a reasonable objection, I could replace "loaded" with "compiled" and your non-argument would make just as much sense. The alternative does not make the "complexity" go away, it just distributes across multiple languages in your application and database.
3) No.
4) Another non-argument against stored procedures. For example, suppose I have a table "time_series(series_id INT, tstamp TIMESTAMP, val NUMERIC)". A common need would be to accumulate all points (tstamp, val) associated with a series_id. Following your logic, you either end up with tons of con the application side sending similar variations of a query that looks like "SELECT tstamp, val FROM time_series WHERE series_id = $x ORDER BY tstamp" or you create one application-level module that acts as an abstraction around a query like that. In the first case, you're doing massive duplication. In the second case, you've essentially made a stored procedure that is distributed across your database and application and all the issues you raised of having to write something to talk to it apply just the same.
5) Again, no. DBs are precisely to place to deal with issues like this as they have means for dealing with things like foreign tables. The application-level alternative just means re-inventing it all yourself and you're probably going to make a lot more mistakes and write a lot more code that way.
6) Non-argument (applies just as well to Rails, Python, Linux, etc.)
Not sure why you're getting downvoted. Anecdotally and in my area I can confirm racism and sexism (usually in the form of "harmless jokes") is pretty rampant in tech.
I think the downvotes are due to the fact that we haven't seen any evidence of actual racism or sexism in the tech industry. We see lots of stories like this where it seems open to interpretation.
And yes, I myself have some personal experience of real racism. If this is the worst that is happening in the tech space then things are pretty good.
Anyway, this is an important topic, so if you do have any experiences with racism/sexism it would be good to write an article or blog post about it.
This is fucking horrible. If there was so much as an ounce of truth to all the noise Google has been making about "diversity" over the past couple years, they had better have one hell of an answer for all this very, very soon. And if they don't, well that also is one hell of an answer, although an extremely discouraging one for any of us concerned with fairness and equality in the tech space.
Erica: sharing your experiences the way you did was extremely brave. I can only imagine what you must be going through having already braved such a minefield of abuse in what ought to be a progressive and accepting work environment. Keep fighting the good fight.
Transgender people are probably more hated than any other minority and hate-speech that would be completely unacceptable made about any other group often goes unchallenged when made about members of the transgender community. So it's not at all surprising a member of this group is having trouble finding her legal defence. And that's a problem.
I'm not sure Bradley Manning would have had a considerably bigger chance of getting pro bono defense than Chelsea Manning does now. Her transition may be a factor, but I'd wager it's not the biggest one by far -- even Snowden is widely regarded as a traitor in the US and he was considerably more nuanced about what confidential information he handed to the press.
>Transgender people are probably more hated than any other minority
They are the second most hated. The most hated is the one hate groups compare all other minorities to when attacking them. The catch is that the most hated group has far better ability to pass than transgender individuals, meaning that a 'which group is worse off' classification is harder to determine.
Stop it. Woman do not somehow have to share the blame for their husbands alleged misdeeds. Seriously, this is 2015, not the middle ages where they'd burn a woman at the stake for something her husband did wrong.
>Exactly. They seem to forget that she's part of a ponzi scheme, slept with married men to get ahead, etc.
For god's sakes, stop it. This blatant sexism and double standards is disgusting. If Ellen were a man, never in a million years would they be expected to bear responsibility for their spouses' misdeeds or attacked for who they slept with (indeed, they'd be getting high-fived for being a "womanizer" or "stud").
> I don't understand how anyone can defend her and her husband after one of them (allegedly) ruined the pension funds of thousands of clients who trusted them
This is 2015, I really hope you don't need someone to explain to you that women don't have to share the blame for their husbands (alleged) misdeeds. Disgusting.
Based on your comment history I can't tell if you're a troll or just severely misguided. On the off chance that you do legitimately believe this, I'll go ahead and respond.
Fundamentally, you misjudge my stance: I don't care Pao's a woman. If I learned that the woman I married had done that to people, I would not stay with them, because I cannot reconcile being married to someone who can do that with my own ethos. That she has speaks volumes of her character. If Pao had committed fraud, and her husband had stayed with her, I would have the same feelings about him.
(From your comments, I suppose this is the part where you claim that Male White Nerds on the internet always say that, but never do it, etc.)
Second: It's not even just a matter of staying with him, but she has sued a company that turned out to be innocent for sexual discrimination asking for the exact amount in damages that he needs to cover his legal fees. To me, that steps beyond just having suspect character, to outright being complicit in the attempt to prevent him from paying for his crimes.
Pao is disgusting, and it has nothing to do with her gender. Only her actions.
2) This is not a reasonable objection, I could replace "loaded" with "compiled" and your non-argument would make just as much sense. The alternative does not make the "complexity" go away, it just distributes across multiple languages in your application and database.
3) No.
4) Another non-argument against stored procedures. For example, suppose I have a table "time_series(series_id INT, tstamp TIMESTAMP, val NUMERIC)". A common need would be to accumulate all points (tstamp, val) associated with a series_id. Following your logic, you either end up with tons of con the application side sending similar variations of a query that looks like "SELECT tstamp, val FROM time_series WHERE series_id = $x ORDER BY tstamp" or you create one application-level module that acts as an abstraction around a query like that. In the first case, you're doing massive duplication. In the second case, you've essentially made a stored procedure that is distributed across your database and application and all the issues you raised of having to write something to talk to it apply just the same.
5) Again, no. DBs are precisely to place to deal with issues like this as they have means for dealing with things like foreign tables. The application-level alternative just means re-inventing it all yourself and you're probably going to make a lot more mistakes and write a lot more code that way.
6) Non-argument (applies just as well to Rails, Python, Linux, etc.)