Apple Releases Rendezvous As Open Source

clarencek writes "Apple has released Rendezvous as Open Source, as promised. Excerpt: Starting today, developers can download Rendezvous as open source under the Apple Public Source License. Rendezvous is part of a broader Open Source release today from Apple which includes the Darwin 6.0.1 operating system and additional Open Directory plug-ins. Together, these underscore Apple's commitment to making core protocols freely available as open standards and open source."

Comments

yes I have

[johnjones]

infact I wrote in reply to one of your coments if you dont read anything after you write it then....

they HAD to release GCC changes its freaking GPL

I dont hate apple I type this on the family G3

its not compatable with the GPL, that and BSD are my favorite licenses so thats 50% bad

regards

John Jones

google so you have to dont think

Re:APSL takes away rights

[BitGeek]

You don't see the OSS/FS community bitching because Apple ripped off the dock, which is used in so many of our Window Managers, do you? No.

I love how apple "ripped off the dock" from operating systems that were released well after NeXTSTEP.

We all know they have amazing powers of time travel-- "stealing future technology for the needs of today!"

Sheesh.

Nevermind that the entirety of the look and feel of every Linux box is a blatent ripoff of the creation of Apple computer (with a trivial amount licensed from Xerox.)

No, lets pretend that isn't the case. sure.

Something glazed over....

[Brat Food]

One thing that sems to be missing in all of this is that Apple is a public, for profit company, releasing code in to the public domain.

While im sure the GPL et al. are great, what apple does is give themselves some protection, and try to make it so that their code doesnt get forked and messy with no way "keep up" with it. To illustrate the point, lets say rendevous is released under a "take it and do whatever the hell you like" liscense. CompanyA decides to add something, and releases a million widgets with their unpublised modification. Lets also say that this modificaiotn makes their produch not interroperate with anything else based on the standard. Now, while you may say "thats companyA's perogative", you are also probably not realizing that companyA is so often microsoft. So you see, the protection built in stops companyA form "embrace, extend, break" and gives OTHERS using the standard sort of a guarentee that they wont be left out in the cold. If i find a bug, i can be sure that my addition will work with the standard that everyone has. Its not perfect, its not the same on the outside, but, to all you detractors, it has its inherant merits, and should not be judged with tunnel vision.