Hacker News story: Ask HN: Why Databases Instead of Filesystem?

Ask HN: Why Databases Instead of Filesystem?
A database could be described crudely as a program for interfacing with data on disk. Most software is built to interface with databases although the software also has (often very capable) ways of interfacing with data on disk via filesystem interaction. My question is, what historically has driven the industry to focus on database-specific solutions, rather than on filesystem-specific solutions? This is not a rant against databases, but I do wonder why many major programming languages and frameworks (RoR Active Directory, C# EF, etc) have put much effort into making database interaction smooth from the perspective of the programming language, instead of putting effort into interacting with data on disk. Kind of an alternate reality sort of musing. 5 comments on Hacker News.
A database could be described crudely as a program for interfacing with data on disk. Most software is built to interface with databases although the software also has (often very capable) ways of interfacing with data on disk via filesystem interaction. My question is, what historically has driven the industry to focus on database-specific solutions, rather than on filesystem-specific solutions? This is not a rant against databases, but I do wonder why many major programming languages and frameworks (RoR Active Directory, C# EF, etc) have put much effort into making database interaction smooth from the perspective of the programming language, instead of putting effort into interacting with data on disk. Kind of an alternate reality sort of musing.