1) Please stop the never ending slide towards making slashdot into a "modern" graphics heavy website. If I want gizmodo or nbc.com I'll go there on my own.
2) I don't come here for wizbang buzzword features. I come here to READ about them.
3) My preference would be to even scrap the current implementation and go back 4-5 years when the site was much faster and more usable.
4) On the mobile side... you just need to start over. I find it very frustrating to use and have honestly almost removed it from my bookmarks.
The only thing I found flawed in the study was how many seagate drives actually made it through the warranty period.
My personal experience shows a failure rate of seagate drives at around 300-400%(pool of 20-30 drives). What I am saying is that not only did the original drives fail, but the "refurbished" replacements failed as well, numerous times. Not a single drive got through warranty without the nice green border. The amount I spent on advanced replacements could have bought me quite a few new drivers from another vendor.
I no longer buy seagate drives. I do not have any abnormal failure rates on the other brands I use.
If I fix a computer, I don't get royalties for life. Drm is a false economy where infinite supply is a given, so consumption is metered. How could you possibly justify this
I'm not.... not sure I ever will be again. I have long supported nukes for power as a good alternative to our many other heavily polluting technologies. But I was over looking a major detail. The systems are not and cannot be fail safe.
At the same time, there is no other competing technology that has anything close to the potential downside that nuclear energy has. I always worried about reactor control, and never really gave much thought to the holding pools. But the pools have much more fuel, and are not heavily protected. If cooling is disrupted, even when everything is "shut down", you are looking at a horrible disaster. Its not worth it.
As a parent with a mentally disabled child, I do not agree.
Our children live in a world still devoid of danger and threat. They expect us, their elders to protect them from harm. That falls to the caretakers as well as us parents. Since we parents have little choice as far as where our children are housed everyday, we have to make other choices and decisions.
I do not see this as an over reaction. I see it as well thought out, and keeping the idea of the child's privacy in mind. The solutions that are out there and available to us today are poor worst, expensive at best. Considering whats available off the shelf, this should be doable on your own.
Does anyone here have any valuable advice other than satire and sensationalism? I could use it myself. I'm just as lost as the poster, and in desperate need.
There is nothing wrong with the viewer. I find it comical that you would think that I would WANT to go "back" to windows media. It's basically the same thing in a different DRM wrapper.
Anyways. I'm not "up in arms". Just streamin my TV seasons the same way I have been for months.
Decent TTS in a widely-used device will basically kill the audiobook market, and authors should be compensated in some way for the revenue lost there. What's wrong with that?
No. They should not. Society moves on. Those left behind need to ask themselves why. Maybe they were never needed in the first place?
I see no reason AT ALL to ever protect dead markets OR the people who steadfastly insist to keep working in them.
Let them go down with their ship. It's their ship after all. It's their choice.
Well... then they better try again. It still sounds like a complete failure to me. Since the integrated graphics is equivalent, there is no advantage, and no resolution to the problem. What exactly are you try to get at?
The point of copy right is not to temporarily restrict peoples access to information. It's designed to guarantee ownership, credit, and monetization to those who created it during their life time.
Copyright laws were designed to prevent the destructive nature of ideas like DRM. The ideas behind DRM are not new. Just the D is.
So here is the deal... DRM is inherently illegal. It grants perpetual copyright to any item encoded with it. Anyone know how your are going to play your itunes music in 2108? How about playing a record from 1908. One is interesting. The other is impossible.
The locks make copyrighted works "expire". How exactly are works supposed to become part of the public lexicon if they are scrambled when they get there?
How about this? It's at the bottom of the first page of the first link.
----- "Vehicles competing in the Urban Challenge will have to think like human drivers and continually make split-second decisions to avoid moving vehicles, including robotic vehicles without drivers, and operate safely on the course. The urban setting adds considerable complexity to the challenge faced by the robotic vehicles, and replicates the environments where many of today's military missions are conducted."
Sounds to me like you are the problem. That's a heinous comment.
Patching is dangerous. It is not for the foolhardy, or ignorant. Your IT department is there to protect you from the "just do it" mentality. Trust them, and when they wine about problems in the process, take heed.
Our systems have been taken down twice this year due to bad patches from good old MS. Patches that we in IT were FORCED to deploy before proper testing. Guess who has control of the process in our organization now?
Protected memory helps not at all as long as you are using shared dlls. In a multitasking environment, if a process flags a semaphore, and crashes before releasing, how do you get rid of it? You reboot. This is the joy of the of embedding your brower as a root level service. Having it vulnerable is just icing on the cake. When explorer burps, windows crashes down around your neck. Switching to Firefix has eliminated this frustration for me BTW.
I am actually happier with windows now than I ever have been in the past. Maybe Microsoft should bundle Firefox with Windows. It makes a dang nice machine!
This has been going on for at least wo weeks. You can get to the download.microsoft.com by appending "c.footprint.net" on the end of the server address. So, the link becomes:
If your program causes a blue screen, it's your fault! I don't care if you simply called a win32 API called BSOD. As far as I am concerned, if you write software it is your responsibility to make sure that the machine does not crash on your cpu cycle. No blaming it on the API you are using either. If you know that the API causes the crash, then change APIs on pull your program. simple as that. If there are no remaining APIs available, then you better write your own code, or again, pull your software.
I find it absolutely infuriating that this windows word thinks it's just fine to "leverage" thirdparty APIs and play stupid when they fail. Guess what! Microsoft writes buggy software! Maybe you shouldn't jump in to bed with them just to save time on development.
Here is another idea, maybe you should hold the API developer responsible when the API crashes YOUR computer during development!
This has to stop somewhere. The way we are going right now, it will be some stupid overbearing government regulation that puts the industry in a noose. Is that what you want? No? Then stop the insanity!
Slashdot Mirror
1) Please stop the never ending slide towards making slashdot into a "modern" graphics heavy website. If I want gizmodo or nbc.com I'll go there on my own.
2) I don't come here for wizbang buzzword features. I come here to READ about them.
3) My preference would be to even scrap the current implementation and go back 4-5 years when the site was much faster and more usable.
4) On the mobile side... you just need to start over. I find it very frustrating to use and have honestly almost removed it from my bookmarks.
The only thing I found flawed in the study was how many seagate drives actually made it through the warranty period.
My personal experience shows a failure rate of seagate drives at around 300-400%(pool of 20-30 drives). What I am saying is that not only did the original drives fail, but the "refurbished" replacements failed as well, numerous times. Not a single drive got through warranty without the nice green border. The amount I spent on advanced replacements could have bought me quite a few new drivers from another vendor.
I no longer buy seagate drives. I do not have any abnormal failure rates on the other brands I use.
If I fix a computer, I don't get royalties for life. Drm is a false economy where infinite supply is a given, so consumption is metered. How could you possibly justify this
I'm not.... not sure I ever will be again. I have long supported nukes for power as a good alternative to our many other heavily polluting technologies. But I was over looking a major detail. The systems are not and cannot be fail safe.
At the same time, there is no other competing technology that has anything close to the potential downside that nuclear energy has. I always worried about reactor control, and never really gave much thought to the holding pools. But the pools have much more fuel, and are not heavily protected. If cooling is disrupted, even when everything is "shut down", you are looking at a horrible disaster. Its not worth it.
You run a server of any kind. In the old days of novell, we had severs with 6 year uptimes. Not possible today simply from patches, not crashes.
This service has the potential to get us closer to that ever distant 100% uptime. It could definately stack another 9 on 99.999
As a parent with a mentally disabled child, I do not agree.
Our children live in a world still devoid of danger and threat. They expect us, their elders to protect them from harm. That falls to the caretakers as well as us parents. Since we parents have little choice as far as where our children are housed everyday, we have to make other choices and decisions.
I do not see this as an over reaction. I see it as well thought out, and keeping the idea of the child's privacy in mind. The solutions that are out there and available to us today are poor worst, expensive at best. Considering whats available off the shelf, this should be doable on your own.
Does anyone here have any valuable advice other than satire and sensationalism? I could use it myself. I'm just as lost as the poster, and in desperate need.
has anyone else actually checked to see if this article is true?
There is nothing wrong with the viewer. I find it comical that you would think that I would WANT to go "back" to windows media. It's basically the same thing in a different DRM wrapper.
Anyways. I'm not "up in arms". Just streamin my TV seasons the same way I have been for months.
Decent TTS in a widely-used device will basically kill the audiobook market, and authors should be compensated in some way for the revenue lost there. What's wrong with that?
No. They should not. Society moves on. Those left behind need to ask themselves why. Maybe they were never needed in the first place?
I see no reason AT ALL to ever protect dead markets OR the people who steadfastly insist to keep working in them.
Let them go down with their ship. It's their ship after all. It's their choice.
Please specify where i can hire a citrix admin for 5k a year salary... forget two.
orly? Price fixing? Extortion? Abuse of power? Collusion?
Does this open your eyes?
This actually isn't true, although it was the exact analogy I was always taught.
It's much more complex, and beyond the scope of a sd post. Mind boggling actually.
Well... then they better try again. It still sounds like a complete failure to me. Since the integrated graphics is equivalent, there is no advantage, and no resolution to the problem. What exactly are you try to get at?
* Citation needed.
I just read Article IV again to be sure... but I don't see it "explicitly" here.
All the things above are in preparation for killing people. Nothing our military does saves lives. That would be oxymoronic.
This new duty on the other hand DOES SAVE LIVES.
Citation missing...
In my entire career I have never heard of anything close to this. Please cite sources.
We have no problems here at all with over 300 users behind 1 ip. None. Zip. Zero.
Huge networks use Nat all the time to handle merging of incompatible networks. I have no idea what you could possibly be talking about. I call FUD.
The point of copy right is not to temporarily restrict peoples access to information. It's designed to guarantee ownership, credit, and monetization to those who created it during their life time.
Copyright laws were designed to prevent the destructive nature of ideas like DRM. The ideas behind DRM are not new. Just the D is.
So here is the deal... DRM is inherently illegal. It grants perpetual copyright to any item encoded with it. Anyone know how your are going to play your itunes music in 2108? How about playing a record from 1908. One is interesting. The other is impossible.
The locks make copyrighted works "expire". How exactly are works supposed to become part of the public lexicon if they are scrambled when they get there?
How about this? It's at the bottom of the first page of the first link.
-----
"Vehicles competing in the Urban Challenge will have to think like human drivers and continually make split-second decisions to avoid moving vehicles, including robotic vehicles without drivers, and operate safely on the course. The urban setting adds considerable complexity to the challenge faced by the robotic vehicles, and replicates the environments where many of today's military missions are conducted."
I wish you were joking.
It is not an innovation by it's mere existance, but by nature of proper implementation, that increases value.
UAC is a great example of an innovative idea that was implemented wrong. It diminishes the value of the OS.
All this "signing" in windows has really cut down on the viruses right? No? Why? Implementation!!!
Sounds to me like you are the problem. That's a heinous comment.
Patching is dangerous. It is not for the foolhardy, or ignorant. Your IT department is there to protect you from the "just do it" mentality. Trust them, and when they wine about problems in the process, take heed.
Our systems have been taken down twice this year due to bad patches from good old MS. Patches that we in IT were FORCED to deploy before proper testing. Guess who has control of the process in our organization now?
I'm glad you love yourself. Here is the answer.
Protected memory helps not at all as long as you are using shared dlls. In a multitasking environment, if a process flags a semaphore, and crashes before releasing, how do you get rid of it? You reboot. This is the joy of the of embedding your brower as a root level service. Having it vulnerable is just icing on the cake. When explorer burps, windows crashes down around your neck. Switching to Firefix has eliminated this frustration for me BTW.
I am actually happier with windows now than I ever have been in the past. Maybe Microsoft should bundle Firefox with Windows. It makes a dang nice machine!
You try spinning your building at 8000 RPM for the "spin application" process.
and a narative
Access Floors
This has been going on for at least wo weeks. You can get to the download.microsoft.com by appending "c.footprint.net" on the end of the server address. So, the link becomes:
n load/1/8/f/18f8 cee2-0b64-41f2-893d-a6f2295b40c8/TW04006_WINHEC200 4.ppt
http://download.microsoft.com.c.footprint.net/dow
Go figure. I have no idea excatly why this is happening. I'll leave that to people who care.
News flash buddy!
If your program causes a blue screen, it's your fault! I don't care if you simply called a win32 API called BSOD. As far as I am concerned, if you write software it is your responsibility to make sure that the machine does not crash on your cpu cycle. No blaming it on the API you are using either. If you know that the API causes the crash, then change APIs on pull your program. simple as that. If there are no remaining APIs available, then you better write your own code, or again, pull your software.
I find it absolutely infuriating that this windows word thinks it's just fine to "leverage" thirdparty APIs and play stupid when they fail. Guess what! Microsoft writes buggy software! Maybe you shouldn't jump in to bed with them just to save time on development.
Here is another idea, maybe you should hold the API developer responsible when the API crashes YOUR computer during development!
This has to stop somewhere. The way we are going right now, it will be some stupid overbearing government regulation that puts the industry in a noose. Is that what you want? No? Then stop the insanity!