I have to quibble with the "standard" computer term here. Microsoft is going to require 64-bit CPUs for server projects, not desktop products. By 2008 when any of these projects ships, it will probably be difficult to even purchace a server that does not support 64-bit memory addressing.
Wait a sec. Are you saying that drivers run in a user mode process? Cause that is just plain wrong. Drivers run in kernel space. Hence why they have to handle things like non-paged memory, disabling interrupts, etc, etc.
Um, You will have to pardon my ignorance here, but since when have device drivers ever been outside of the kernel in a Windows OS? At least in NT 4.0 and beyond (I'm too young to know any earlier), they always run in kernel space as far as I know.
The original Windows NT architecture might have been a microkernel. But ever since the 4.0 version where Microsoft pulled the video subsystem into kernel space, there is no way you can still call that a microkernal. And they have only been pulling more and more into kernal space (for example, large portions of the IIS 6.0 HTTP processor actually run in kernel space on Windows Server 2003).
<sarcasm>Yes, because their are just such a pethera of other ways to make any money selling Linux that getting rid of the tech support side of the house would make everything a lot simpler.</sarcasm>
Great. As soon as you figure out how to harness all that zero point energy that is just lying around and come up with a way for NO one to work, you let us know and we will get to work creating that communist state:)
It's not embrace and extend when the guy that created the RSS standard (Dave Winer), has a post up today about how Microsoft specifically asked him if it would be ok to extend the spec before going down this path and how he thought this would be a good addition to the RSS spec.
From the article: "The story begins in March of this year. I got a call from Robert Scoble saying there was a group on the MSIE team that wants to extend RSS to handle lists. I was immediately supportive of this, I told Scoble that some people think I'm conservative about extending RSS, but I'm actually liberal. The only thing I don't like is when people invent new ways of expressing data that RSS already defines. He assured me this isn't what was going on."
Uh....sorry. Perhaps I am being naive here, but what privacy rights did we give up to arrest these guys? Heck, I'll challenge you to point out a privacy right that was violated in this case.
Sadly, the shorter development cycles for these platforms means that these developers have less and less time to mount those sorts of learning curves. We seem to be entering an era where game developers need to relearn their skills every 3-4 years or so.
Multithreading IS hard if you are sharing any state between the threads. And the difficulty in debugging multithreaded issue in a large/complex application (i.e., any commercial game these days) goes up by at least an order of magnitude with the introduction of true multi-threading via 2 cores. On a single processor machine, you can get away with more because you don't have true concurrency. And in your particular case, you actually have no concurrency so it is even easier. But if you want to be truely scalable and try to squeeze as much out of that second processor as possible, you have to deal with all sorts of problems like deadlock, write barriers, critical sections, etc. These are HARD issues, not least because many of the bugs these issues can introduce are both hard to wrap your head around and because the issues will only expose themselves when you get an unlucky context switch at just the right moment in execution.
Legally, companies can and are routinely held responsible for the conduct of their employees. For example, lets saw one of your employees is driving around in a company truck and hits someone. The company, not the individual is sued. It does not matter if the employer repeated told that employee not to drive, and it does not matter if the company knew whether this employee was a "good" driver or not.
Bottom line, a company is responisble for laws broken with its equipment. The same rule would apply here.
I think it is also important to note that a GUID is NOT a security hole. That would be like saying having a MAC address on your network card is a security hole. It may be a privacy hole, but it does not effect the security of your system.
Ok, lets go the other way. Lets say I am an international shipping company. I agree that you can send anything you want on my trucks, and I will not report them to customs. Is that legal? Whats the difference? Where do you draw the line?
And what is with the comment, "if you can't prove it's legal, we can't let you transfer it"? Since when? Napster was given a PRECISE list of songs that it was not allowed to trade. Anything not on that list was perfectly free for trading. Napster does not block access to any song that it is unaware of.
You can also tape songs of the radio for free, yet most people buy CDs anyways.
But there is an inherent difference between taping from the radio and downloading from the internet.
1) Radio does not sound as good as a CD (mp3 does not suffer from this problem)
2) In order to tape from the radio, I have to sit in my room waiting deseperatly for the station to play the one song I want.
This is why radio recordings have never been a big business. You could not do on a grand enough scale to hurt anyone's profit margins.
p2p costs a TREMENDOUS amount of money in terms of sales. As I said before, no one will pay for something they get for free (assuming they are rational). p2p as a advertising buget? No offense, but that is what the radio is. free advertising, and free listening for the consumer (more or less). But the difference is that the radio is much more controlled: only certain songs are put up, and they are of lesser quality than those found on the average CD. The Music industry does not need another service for that.
But the internet and MP3 files make it profitable to sell just 10 (copies).
But they only do that if the 10 copies are actually paid for. This is problem that everyone seems to miss.
How about making the entire catalogs of their recordings older than one year available online for $5/month
Again, how long will that sort of system generate revenue? Once most of the songs are on the interent (and by and large, any recording older than 1 year old is already on the various file sharing systems), the revenue stream would dry up.
Look, lets be honest. People will not pay for things that they can get it for free (provided that punishment is negligle). Until the RIAA and those sorts of groups start publicly suing anyone they find with copyrighted songs illegally aqcuired (aka, non fair use), this problem will continue. And since the determining the difference between fiar use and non fair use is difficult to determine, the problem is going to continue.
Slashdot Mirror
You've just explained the whole reason why Microsoft released Beta 1 and now Beta 2: So that web site designers could update their HTML.
I have to quibble with the "standard" computer term here. Microsoft is going to require 64-bit CPUs for server projects, not desktop products. By 2008 when any of these projects ships, it will probably be difficult to even purchace a server that does not support 64-bit memory addressing.
Wait a sec. Are you saying that drivers run in a user mode process? Cause that is just plain wrong. Drivers run in kernel space. Hence why they have to handle things like non-paged memory, disabling interrupts, etc, etc.
Um, You will have to pardon my ignorance here, but since when have device drivers ever been outside of the kernel in a Windows OS? At least in NT 4.0 and beyond (I'm too young to know any earlier), they always run in kernel space as far as I know.
The original Windows NT architecture might have been a microkernel. But ever since the 4.0 version where Microsoft pulled the video subsystem into kernel space, there is no way you can still call that a microkernal. And they have only been pulling more and more into kernal space (for example, large portions of the IIS 6.0 HTTP processor actually run in kernel space on Windows Server 2003).
<sarcasm>Yes, because their are just such a pethera of other ways to make any money selling Linux that getting rid of the tech support side of the house would make everything a lot simpler.</sarcasm>
I've got a tin foil hat with your name on it when you need that too. Microsoft plant...shesh.
Great. As soon as you figure out how to harness all that zero point energy that is just lying around and come up with a way for NO one to work, you let us know and we will get to work creating that communist state:)
It's not embrace and extend when the guy that created the RSS standard (Dave Winer), has a post up today about how Microsoft specifically asked him if it would be ok to extend the spec before going down this path and how he thought this would be a good addition to the RSS spec.
# a634
http://www.reallysimplesyndication.com/2005/06/22
From the article: "The story begins in March of this year. I got a call from Robert Scoble saying there was a group on the MSIE team that wants to extend RSS to handle lists. I was immediately supportive of this, I told Scoble that some people think I'm conservative about extending RSS, but I'm actually liberal. The only thing I don't like is when people invent new ways of expressing data that RSS already defines. He assured me this isn't what was going on."
Uh....sorry. Perhaps I am being naive here, but what privacy rights did we give up to arrest these guys? Heck, I'll challenge you to point out a privacy right that was violated in this case.
Sadly, the shorter development cycles for these platforms means that these developers have less and less time to mount those sorts of learning curves. We seem to be entering an era where game developers need to relearn their skills every 3-4 years or so.
Multithreading IS hard if you are sharing any state between the threads. And the difficulty in debugging multithreaded issue in a large/complex application (i.e., any commercial game these days) goes up by at least an order of magnitude with the introduction of true multi-threading via 2 cores. On a single processor machine, you can get away with more because you don't have true concurrency. And in your particular case, you actually have no concurrency so it is even easier. But if you want to be truely scalable and try to squeeze as much out of that second processor as possible, you have to deal with all sorts of problems like deadlock, write barriers, critical sections, etc. These are HARD issues, not least because many of the bugs these issues can introduce are both hard to wrap your head around and because the issues will only expose themselves when you get an unlucky context switch at just the right moment in execution.
I think that movie sullies the good name of "poorly"...
Legally, companies can and are routinely held responsible for the conduct of their employees. For example, lets saw one of your employees is driving around in a company truck and hits someone. The company, not the individual is sued. It does not matter if the employer repeated told that employee not to drive, and it does not matter if the company knew whether this employee was a "good" driver or not.
Bottom line, a company is responisble for laws broken with its equipment. The same rule would apply here.
Actually, I think his questions implied that they SHOULD NOT, not necessarily that they do not.
mmm.....Porn a million times faster...
I think it is also important to note that a GUID is NOT a security hole. That would be like saying having a MAC address on your network card is a security hole. It may be a privacy hole, but it does not effect the security of your system.
Ok, lets go the other way. Lets say I am an international shipping company. I agree that you can send anything you want on my trucks, and I will not report them to customs. Is that legal? Whats the difference? Where do you draw the line?
And what is with the comment, "if you can't prove it's legal, we can't let you transfer it"? Since when? Napster was given a PRECISE list of songs that it was not allowed to trade. Anything not on that list was perfectly free for trading. Napster does not block access to any song that it is unaware of.
You can also tape songs of the radio for free, yet most people buy CDs anyways.
But there is an inherent difference between taping from the radio and downloading from the internet.
1) Radio does not sound as good as a CD (mp3 does not suffer from this problem)
2) In order to tape from the radio, I have to sit in my room waiting deseperatly for the station to play the one song I want.
This is why radio recordings have never been a big business. You could not do on a grand enough scale to hurt anyone's profit margins.
p2p costs a TREMENDOUS amount of money in terms of sales. As I said before, no one will pay for something they get for free (assuming they are rational). p2p as a advertising buget? No offense, but that is what the radio is. free advertising, and free listening for the consumer (more or less). But the difference is that the radio is much more controlled: only certain songs are put up, and they are of lesser quality than those found on the average CD. The Music industry does not need another service for that.
But the internet and MP3 files make it profitable to sell just 10 (copies).
But they only do that if the 10 copies are actually paid for. This is problem that everyone seems to miss.
How about making the entire catalogs of their recordings older than one year available online for $5/month
Again, how long will that sort of system generate revenue? Once most of the songs are on the interent (and by and large, any recording older than 1 year old is already on the various file sharing systems), the revenue stream would dry up.
Look, lets be honest. People will not pay for things that they can get it for free (provided that punishment is negligle). Until the RIAA and those sorts of groups start publicly suing anyone they find with copyrighted songs illegally aqcuired (aka, non fair use), this problem will continue. And since the determining the difference between fiar use and non fair use is difficult to determine, the problem is going to continue.