However this "meeting" makes your wonder if this is a community project anymore, there are hundreds of kernel hackers out there, who have in some way contributed code to the kernel
however only 65 get to attend this meeting..
Of course it's still a community project, and yes, there are a lot of people out there that have contributed to writing the kernel for our favorite OS, and no, they weren't invited to this meeting. However, I do see a need to not allow any Tom, Dick and Harry to show up to some of these get togethers. I don't see much progress being made when you have 300 people in a room together all screaming about his or her own agenda... no, you have to trim it down a bit if you really want things to get done. I completely understand where these guys are coming from.
Napster is a protocol for sharing files between users. With Napster, the files stay on the client machine, never passing through the server. The server provides the ability to search for particular files and initiate a direct transfer between the clients. In addition, chat forums similar to IRC are available. OpenNap extends the Napster protocol to allow sharing of any media type, and the ability to link servers together.
opennap is a server for connecting the clients together, and is not a client itself. If you are looking for a client, see the list below.
I hope that they don't strike opennap down. opennap should be a good test for fair use.
The differnece is that Microsoft has a poor track record for supporting alternate platforms. Java, OTOH, has been ported to quite a few architectures. As of right now, the only platform that Microsoft has contributed to at all outside of the Windows OS is MacOS, and Microsoft probably only did that because of the fact that they no longer perceive MacOS as a threat to their dominance in the desktop market.
Also, Java applications run inside of a virtual machine which places a good, thick layer of abstraction between the Java apps that you and I would write and the hardware/OS of the underlying platform. From what I've heard,.NET does not put a layer of abstraction between the platform and.NET programs, so if any cross-platform work has to be done from.NET to any other environment... well, you're pretty much SOL, because porting will require source code modification. From what it looks like to me,.NET is language independant but not platform independant.
Slashdot Mirror
However this "meeting" makes your wonder if this is a community project anymore, there are hundreds of kernel hackers out there, who have in some way contributed code to the kernel however only 65 get to attend this meeting ..
Of course it's still a community project, and yes, there are a lot of people out there that have contributed to writing the kernel for our favorite OS, and no, they weren't invited to this meeting. However, I do see a need to not allow any Tom, Dick and Harry to show up to some of these get togethers. I don't see much progress being made when you have 300 people in a room together all screaming about his or her own agenda... no, you have to trim it down a bit if you really want things to get done. I completely understand where these guys are coming from.
Wow...
Napster is a protocol for sharing files between users. With Napster, the files stay on the client machine, never passing through the server. The server provides the ability to search for particular files and initiate a direct transfer between the clients. In addition, chat forums similar to IRC are available. OpenNap extends the Napster protocol to allow sharing of any media type, and the ability to link servers together.
opennap is a server for connecting the clients together, and is not a client itself. If you are looking for a client, see the list below.
I hope that they don't strike opennap down. opennap should be a good test for fair use.
The differnece is that Microsoft has a poor track record for supporting alternate platforms. Java, OTOH, has been ported to quite a few architectures. As of right now, the only platform that Microsoft has contributed to at all outside of the Windows OS is MacOS, and Microsoft probably only did that because of the fact that they no longer perceive MacOS as a threat to their dominance in the desktop market.
Also, Java applications run inside of a virtual machine which places a good, thick layer of abstraction between the Java apps that you and I would write and the hardware/OS of the underlying platform. From what I've heard, .NET does not put a layer of abstraction between the platform and .NET programs, so if any cross-platform work has to be done from .NET to any other environment... well, you're pretty much SOL, because porting will require source code modification. From what it looks like to me, .NET is language independant but not platform independant.
However, if I'm wrong, please correct me. : )