Why? As the worlds leading contributor to open source and 40 years experience building development tools it is probably the best acquirer. Would you rather Oracle?
Don't confuse gun control with banning guns. If we look at Australia for example, a country often cited in regards to gun control (and I live there), guns are not banned. You can buy a gun, I have family with guns, there are gun shops. But there are restrictions on the type of gun you can buy, 12 gauge shotgun for duck shooting is ok, AR-15 for people shooting is a no go.
But the big difference is the culture, most people in Australia simply don't want to own a gun, it doesn't define who they are. They don't feel threatened or unsafe by not having one.
I am an Azure user and love it, but these articles are comparing apples and oranges. Microsoft, IBM or Oracle include cloud software such as Office 365 or enterprise software such as their ERP systems. Amazon doesn't really even sell comparable software.
One thing people often forget when bagging IE6 is that all browsers were rubbish back then. None followed standards. IE6 was actually a better browser than Netscape and Netscape's next gen browser was too late to be released due to development issues.
According to the people who worked on IE that was never really the intention, it was just assumed from the outside. They intended to create this whole new "amazing" updated browser all baked into Windows that would be maintained and updated. Anyone old enough to remember Windows 98 would remember things like active desktop which was a precursor to this. But legal and technical issues followed and before long they had gone years without a browser update.
> You'll most likely end up implementing an ORM anyway,
This is a really good point. Many people start with the "no ORM" philosophy, realize their application needs some way to map the SQL to the code, time passes..., they have implemented their own half-baked ORM.
A more positive spin is that you'll have an "ORM" that's exactly adapted to your application. Many apps (1) don't need to work with multiple DBMS types and (2) don't use even close to the full panoply of SQL features.
In a language like Java that has a generic DBMS API you can get along just fine with a few classes that handle CRUD operations and transaction management. Somebody familiar with JDBC and SQL can write the bridge classes in about a day, while keeping the overall application vastly simpler.
Either way somebody needs to make an informed choice about ORM vs. direct SQL. It seems as some people get in trouble because they skip that part of the design process.
Because it is not included. You would purchase a base package for say $20 a month, then start adding the apps you want for another $5 a month each. $$profit$$
