andreasg 72151 (10/23/2016)
I follow that stuff also for nearly 30 years... and I want to add "why you don't need another programming language".in my opinion people waste lot of enery and time in inventing "revolutionary" database concepts and languages, thereby neglecting that especially C/C++ (and previously PASCAL) had the idea of being extensible for solve any future programming challenges. Someone who's a full bred programmer can dissemble any problem and code that in C++ - more or less elegant - and it is possible to store everything in a row oriented database.
Over past 30 years colum/row oriented databes (with or without using the "relational thing" were dominant, because nearly all data was provided in that way. And before we had the object oriented world an object was just a "Struct" that could contain other structs or even functions / methods, didn't even need C++ for that. Other things will come and they will go... I'd guess MS SQL server and C++ / C# will still exist even in 30 Years, but everything else will be buried in the /NUL device.
Well, it's the same reason we have other spoken and written languages, dialects and accents of those languages. People use what they are native to and what they feel is clear communication in their area. We all can't move to English, Spanish or something else. In our case, it's what the business users use. However, in most cases, it's just using what make sense for the job.
For example, it does not make sense to use C++ to query data. It's a very complex language and we shouldn't have to write our own binary trees and functions to store, sort and fetch data from. The same may apply to the Python. I can surely use C++ to do everything that I'm doing in Python, but I wouldn't use C++ to prototype a new enterprise application. It's too much work and I accomplish similar objects in C++ with Python with far less code and time.
As I mentioned in previous post, SQL Server is struggling on my end. It's easier to keep scaling up and up with SQL Server. Adding more memory, adding more CPU and other resources to meet my requirements. Sure, there are ways on the application level to distribute process the data. SQL Server also has ways to configure multiple SQL instances to simulate this as well. That's a lot of overhead and extremely expensive on enterprise levels when I can just us another database engine that may be open source and does it more natively.
All are tools that have good uses. Some can pretty much do anything. It doesn't mean it's the right tool for the job though. C++ by far is not the only language we need for every programming project.