I have that wish for humanity: I'd really like people to use words that are in proportion with what they describe.
Things like: "we're dead" (when we just talk about loosing a contract or even closing one company), "it's totally catastrophic" (when someone cannot make it to a meeting, or the vegetables you had planned for dinner are not available anymore at the groceries).
Come on.
Talking about "worst holy war" for tooling trends - sorry, not for me, even for the purpose of creating a catchy headline or of underlining a point.
Oh and yes: I use both NoSQL and SQL, sometimes in conjunction in the same system.
>I use both NoSQL and SQL, sometimes in conjunction in the same system.
As any sane developer would, and without having to go all-or-none either which way. I don't understand the people who are balls to the wall for either side. They both have a purpose.
The fights around "tech X is better than tech Y" usually boil down to some kind of fear (of being replaced, of loosing the job) or biaised-validation of all the effort already invested in X.
I think the article used "worst holy war" in the sense of "lamest". The (No)SQL "holy war" is just as dumb as any other computer-related "holy war" throughout our industry's short history (e.g., emacs/vi, Windows/Mac/Linux/Unix). It's as dumb as the arguments about who the best Captain of the Enterprise was.
Things like: "we're dead" (when we just talk about loosing a contract or even closing one company), "it's totally catastrophic" (when someone cannot make it to a meeting, or the vegetables you had planned for dinner are not available anymore at the groceries).
Come on.
Talking about "worst holy war" for tooling trends - sorry, not for me, even for the purpose of creating a catchy headline or of underlining a point.
Oh and yes: I use both NoSQL and SQL, sometimes in conjunction in the same system.