That is a lot of excitement for something that was available at http://xquartz.macosforge.org/ on release day. I didn't even notice or care until I realized that libpng's headers were considered part of X11.
When Apple introduced X11.app, I regarded it a tactic to get UNIX developers onto the platform. At the time, MacOS developers were sticking to Carbon like glue, and I think that by improving the POSIX compatibility and adding X11, Apple was trying to get other communities excited about OSX.
X11.app did not integrate well with OSX, let alone Apple's shrinkwrap vision of the Desktop. I'm not surprised to see they treat it like an optional add on package, and I am somewhat relieved to see it continue as an open source project with support and recognition by Apple. It's the right way to handle a legacy framework in my opinion.
As for the loss of RSS from Mail.app and Safari.app. Srsly? People use that who don't have a six paragraph definition for "semantic web"?
When Apple introduced X11.app, I regarded it a tactic to get UNIX developers onto the platform. At the time, MacOS developers were sticking to Carbon like glue, and I think that by improving the POSIX compatibility and adding X11, Apple was trying to get other communities excited about OSX.
X11.app did not integrate well with OSX, let alone Apple's shrinkwrap vision of the Desktop. I'm not surprised to see they treat it like an optional add on package, and I am somewhat relieved to see it continue as an open source project with support and recognition by Apple. It's the right way to handle a legacy framework in my opinion.
As for the loss of RSS from Mail.app and Safari.app. Srsly? People use that who don't have a six paragraph definition for "semantic web"?