Editing Enterprise Objects Framework (section)

== History ==
In the early 1990s [[NeXT]] Computer recognized that connecting to databases was essential to most businesses and yet also potentially complex.  Every data source has a different data-access language (or [[Application programming interface|API]]), driving up the costs to learn and use each vendor's product. The NeXT engineers wanted to apply the advantages of [[object-oriented programming]], by getting objects to "talk" to relational databases. As the two technologies are very different, the solution was to create an abstraction layer, insulating developers from writing the low-level procedural code ([[SQL]]) specific to each data source.

The first attempt came in 1992 with the release of Database Kit (DBKit), which wrapped an object-oriented framework around any database. Unfortunately, [[NEXTSTEP]] at the time was not powerful enough and DBKit had serious design flaws.

NeXT's second attempt came in 1994 with the Enterprise Objects Framework (EOF) version 1, a [[Rewrite (programming)|complete rewrite]] that was far more modular and [[OpenStep]] compatible. EOF 1.0 was the first product released by [[NeXT]] using the Foundation Kit and introduced autoreleased objects to the developer community. The development team at the time was only four people: Jack Greenfield, Rich Williamson, Linus Upson and Dan Willhite. EOF 2.0, released in late 1995, further refined the architecture, introducing the editing context. At that point, the development team consisted of Dan Willhite, [[Craig Federighi]], Eric Noyau and Charly Kleissner.

EOF achieved a modest level of popularity in the financial programming community in the mid-1990s, but it would come into its own with the emergence of the [[World Wide Web]] and the concept of [[web application]]s. It was clear that EOF could help companies plug their legacy databases into the Web without any rewriting of that data. With the addition of frameworks to do state management, load balancing and dynamic HTML generation, NeXT was able to launch the first object-oriented Web application server, [[WebObjects]], in 1996, with EOF at its core.

In 2000, Apple Inc. (which had merged with NeXT) officially dropped EOF as a standalone product, meaning that developers would be unable to use it to create desktop applications for the forthcoming [[macOS|Mac OS X]].  It would, however, continue to be an integral part of a major new release of WebObjects.  WebObjects 5, released in 2001, was significant for the fact that its frameworks had been ported from their native [[Objective-C]] programming language to the [[Java (programming language)|Java]] language.  Critics of this change argue that most of the power of EOF was a side effect of its Objective-C roots, and that EOF lost the beauty or simplicity it once had.  Third-party tools, such as [[EOGenerator]], help fill the deficiencies introduced by Java (mainly due to the loss of [[Objective-C#Categories|categories]]).

The Objective-C code base was re-introduced with some modifications to desktop application developers as [[Core Data]], part of Apple's [[Cocoa (API)|Cocoa API]], with the release of [[Mac OS X Tiger]] in April 2005.