Posted by
michael
on from the pipe-dream-or-visionary dept.
miguel writes: "Here is my reply to the various questions on Mono, the future of GNOME and the Register statements." Linux Today has a copy of the email as well.
A well-written clarification
by
Archie+Steel
·
· Score: 0, Redundant
Thanks to Miguel, and a big lemon for the Register for their misleading headline. I guess the search for the "next big scoop" has gotten the better of them this time.
This is all really interesting news...though we should still keep stressing the difference between the ".NET framework" and Microsoft's proposed ".NET services"!
--
Reminder: find a new sig
Re:Alan Cox Says It Best
by
blakestah
·
· Score: 4, Redundant
Microsoft will HAVE to publish APIs etc. for patented features. How else can they get a patent? The whole point behind a patent is that you are granted a 100% legal monopoly for your product IN EXCHANGE for your full disclosure of your product.
Unfortunately, this is the future of proprietary software. Look around at any developing area.
Microsoft has patented the second generation Windows Media Format codecs. Real had patented its codecs. Apple holds exclusive licensing for Sorenson codecs used in Quicktime. So if you want to make or decode a decent video codec, you have to license a patent.
SAMBA is now also encumbered with patents with respect to user authentication. The next generation of Windows will contain this authentication, and the SAMBA team will be unable to make a functional work-alike. Too bad, that is the law.
Unless the Microsoft settlement has something to say about open licensing of patented formats, codecs, and authentication, making software to duplicate new Windows functionality, or providing file or print servers for Windows machines, will become impossible without licensing from Microsoft. You can expect that authentication of users under.NET will use patented protocols, and that they will similarly use other patented protocols into other inter-machine communication APIs. After all, there are a lot of ways to skin a cat; this is one way to keep free software out of Microsoft-monopolized areas.
Thanks to Miguel, and a big lemon for the Register for their misleading headline. I guess the search for the "next big scoop" has gotten the better of them this time.
This is all really interesting news...though we should still keep stressing the difference between the ".NET framework" and Microsoft's proposed ".NET services"!
Reminder: find a new sig
Microsoft will HAVE to publish APIs etc. for patented features. How else can they get a patent? The whole point behind a patent is that you are granted a 100% legal monopoly for your product IN EXCHANGE for your full disclosure of your product.
.NET will use patented protocols, and that they will similarly use other patented protocols into other inter-machine communication APIs. After all, there are a lot of ways to skin a cat; this is one way to keep free software out of Microsoft-monopolized areas.
Unfortunately, this is the future of proprietary software. Look around at any developing area.
Microsoft has patented the second generation Windows Media Format codecs. Real had patented its codecs. Apple holds exclusive licensing for Sorenson codecs used in Quicktime. So if you want to make or decode a decent video codec, you have to license a patent.
SAMBA is now also encumbered with patents with respect to user authentication. The next generation of Windows will contain this authentication, and the SAMBA team will be unable to make a functional work-alike. Too bad, that is the law.
Unless the Microsoft settlement has something to say about open licensing of patented formats, codecs, and authentication, making software to duplicate new Windows functionality, or providing file or print servers for Windows machines, will become impossible without licensing from Microsoft. You can expect that authentication of users under