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…
>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.
NoSQL v. SQL is the worst holy war ever.
31–40 of 59 posts
Re: NoSQL v. SQL is the worst holy war ever.
#32The whole idea with "NoSQL" is that you pick the best tool for the job. Most people that push RDBMS solutions try to shoehorn an RDBMS for every possible scenario. For modeling the majority of business data, an RDBMS is fine. There are many problems such as graphs, logs, lossy real-time data, etc that CAN be modeled in an RDBMS but shouldn't be.
Re: NoSQL v. SQL is the worst holy war ever.
#33The whole idea with "NoSQL" is that you pick the best tool for the job. Most people that push RDBMS solutions try to shoehorn an RDBMS for every possible scenario. For modeling the majority of business data, an RDBMS is fine. There are many problems such as graphs, logs, lossy real-time data, etc that CAN be modeled in an RDBMS but shouldn't be.
The whole idea with "NoSQL" is that you pick the best tool for the job.
Stop it. You're doing it again.The whole idea of "Computer Programming" is that you pick the best tool for the job. It has nothing to do with NoSQL.
Re: NoSQL v. SQL is the worst holy war ever.
#34I 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…
Re: NoSQL v. SQL is the worst holy war ever.
#35I'm going to declare something else the worst holy war ever. Then we can have an even worse holy war than ever was before, making ourselves both wrong.
Re: NoSQL v. SQL is the worst holy war ever.
#36The whole idea with "NoSQL" is that you pick the best tool for the job. Most people that push RDBMS solutions try to shoehorn an RDBMS for every possible scenario. For modeling the majority of business data, an RDBMS is fine. There are many problems such as graphs, logs, lossy real-time data, etc that CAN be modeled in an RDBMS but shouldn't be.
The whole idea with "NoSQL" is that you pick the best tool for the job. Stop it. You're doing it again. The whole idea of "Computer Programming" is that you pick the best tool for the job. It has nothing to do with NoSQL.
Re: NoSQL v. SQL is the worst holy war ever.
#37Re: NoSQL v. SQL is the worst holy war ever.
#38Earlier quoted context omitted.
Deployment isn't the issue with these - deployment can be automated just as easily as an RDBMS. Sometimes easier. It's trivial to throw up several instances of MongoDB for example. As for hosting solutions that support this stuff, well, I prefer VPSs that I control to shared hosting with Mysql for anything that's serious. But you and I appear to have very different needs.
I prefer VPSs too, but if you aim wider auditory you should at least try to support web hosting. With RDBMS it is easy. And with NoSQL it is almost impossible. Maybe this is just a matter of time, when NoSQL will be as much widely used as MS SQL for example, then maybe you will be able to use MongoDB in a web hosting.
Re: NoSQL v. SQL is the worst holy war ever.
#39The whole idea with "NoSQL" is that you pick the best tool for the job. Most people that push RDBMS solutions try to shoehorn an RDBMS for every possible scenario. For modeling the majority of business data, an RDBMS is fine. There are many problems such as graphs, logs, lossy real-time data, etc that CAN be modeled in an RDBMS but shouldn't be.
The whole idea with "NoSQL" is that you pick the best tool for the job. Stop it. You're doing it again. The whole idea of "Computer Programming" is that you pick the best tool for the job. It has nothing to do with NoSQL.
Re: NoSQL v. SQL is the worst holy war ever.
#40I'm going to declare something else the worst holy war ever. Then we can have an even worse holy war than ever was before, making ourselves both wrong.
Neither side will ever give an inch, and vast armies of anonymous have lobbed internets at each other, killing a few StarCraft players in Korea and memeing millions upon millions more, with more arriving every day.