Talk:Extension conflict

Untitled
"Extension conflicts came to an end with the release of Mac OS X, which does not use extensions."

Then what do we call a kext? Isn't that an extension of a sort? —Preceding unsigned comment added by 66.93.55.161 (talk • contribs) 01:18, 26 May 2005

"Especially System 7": As I recall, extensions were not a problem under System 7. The extensions supplied with the system were few and well named, so by glancing over your extensions folder, you knew what was going on in there. However, beginning with Mac OS 7.5.3 (which introduced OpenTransport), the system of shared libraries (such as OpenTransport) began to spread to the Mac OS and installers started to dump dozens of vaguely named things (which usually didn't bear a comment tag of any value) into the extensions folder. By MacOS 8.5 / 9, the extensions folder indeed had become an enigma that for the first time temped MacOS-users to "clean install" their system because of the appearently impossible task of tidying up this mess. —Preceding unsigned comment added by 84.137.137.89 (talk • contribs) 22:26, 15 August 2005

Yes, worst of all was when people began using multiple libraries that all had to be active or inactive at once (instead of one single library, which would be functionally identical) and dropping “shared libraries” that were only actually used by 'one program into the System folder (instead of just integrating them into the program or keeping them in a folder near the program,) all just so that they wouldn't have to recompile the main program, which is a major no-no on Macs since that's exactly what the main program has resource forks to prevent. 72.235.10.209 (talk) 19:05, 28 February 2009 (UTC)

Improvements
Why does "Extensions Manager" redirect to here? I would like it to have a separate article with History. I remember the original Extensions Manager before Apple acquired it and included it with the OS. Connectionfailure (talk) 08:08, 18 March 2008 (UTC)