Not everything is an object. Also you should try coding against both object and graph dbs from an (OO) domain model.
Object identity is a fundamental problem that has nothing to do with the fact that a RDBMS is your persistent back-end.
Also, consider the notion of 'dirty' objects as just one of the problems.
Finally, you still have to manage (to some extent; per your db ymmv) relationship semantics.
Object and graph dbs shine where you wish to traverse your object graph. That is what is painful (and entirely alien) to RDBMS notions.
So if your application domain is naturally mapped to traversal semantics, then it is simpler (but note that you certainly can write complex joins that would support the same) and more importantly, the db engine is tuned to be highly efficient for such use cases.
In the general sense, you are correct regarding the possibility bottom up order. But the bottom falls out from the argument given that the 'context' in question e.g. "political+social set up" is (conceptually) very much the principle object of the conspiracy.
The echo chamber is very important and as with inbreeding appreciated not for its expected failures but rather for exceptional specimens that narrowly and forcefully focus the group thought's essential truth (there's always a germinal factual core somewhere in there) and approach.
We do not have an echo chamber in NYC. But that's because we don't have petri dishes.
What Google is doing is exactly the same thing Microsoft tried with Java (TM:). And Google is not doing Java community any favors by fragmenting the platform. Google is a behemoth filled to gills with paper money.
All these facts make the (contrary) popular reaction quite interesting from a psychological point of view. Image is everything, after all.
My read of it was that systems 'like' Unix are in a cooperative relationship with their end-users, and are not the 'servant'. This burden on the user is rewarded with the 3 cited characteristics.
He further framed this relationship in terms of "dated" main frame style programming and concerns -- scarce computational resources and subsequent minimalist (some would say cryptic) approach to defining the API for the OS.
The point is that that pretty shiny GUI is not as stable as the underlying OS. But the reward here is that the "system" is in a master-servant relationship. ("man pages" ...)
Quite strange that we need to rely on BP to get the facts. (That's like asking the thief to assess damages to his victimes).
I just don't get it.
When someone wants to build yet another strip mall, the State can come in with Eminent Domain in hand and take over private property. If there ever was a case of Eminent Domain, then surely this is it. Seize the damn thing temporarily and have Military tell BP what to do and monitor them 24/7. Once its fixed and they have paid the fines, they can have their "property" back.
Meaningful answers to questions such as "Should I study CS?" are critically informed by the questioner.
Obviously, if you want to make a living in IT and already know how to code, heck, get to work and make money instead of giving it to some corporation masquerading as an "institution of higher learning".
But if your ambition in life includes 'solving the tough problems in computer science', then by all means, pick a top notch school and be diligent in sucking brain content from peers and faculty. Its is not a trivial intellectual domain, and the "primitiveness" of the discipline is actually indicative of how early in the game this thing is.
So , wanna to be the Plato of Computer Science? Either way, you'll need to get that "computer science" education. From the ground up.
A call is invoking a known method bound to the object. In a call based system, the semantics of the object are defined by its interface.
A message is invoking a universal message receiver method bound to all object. Semantics are determined by message content processing. (c.f. "meta boundaries").
It seems accurate then to say "message passing is a specialized form of method invocation that relies on a universal receiver method and delegates the invocation of object methods to the receiver.
