We now have built-in support for data (sets) manipulation in C# and Entity Framework makes things like db.Customers.First().FirstName with syntax support totally real. Many of the premises these essays seem to be based on (like "the languages in play lack any real specialized data structures") are just not true anymore.
Also, I would like to know more about why using an ORM like EF would force me to "have an incredibly stupid schema".
Now that I can agree with, but I would consider that to be a (subtly, perhaps) different position than:
"ORMs are inherently stupid".
IF you have the option of choosing a native object store for persisting objects, then - by all means - choose it. But in cases where an RDBMS is the data store of choice for whatever reason, and you still have to store your objects there one way or another, I'd prefer using an ORM like Hibernate over hand-rolling all the low-level SQL/JDBC code to marshall objects back and forth between the DB.
Turning a powerful SQL database engine into an object storage emulator is just sad.
If your underlying data suits objects better than sets, consider using something that's designed for the job, like one of the many non-SQL database systems.
http://blogs.tedneward.com/2006/06/26/The+Vietnam+Of+Compute...Well worth reading.
Also:
http://database-programmer.blogspot.com.au/2010/12/historica...
http://www.codinghorror.com/blog/2006/06/object-relational-m...