... they break. Then both the 0's and the 1's cannot get through. Result: no sound, no picture. I had a very cheap HDMI cable from a low end retailer which simply fell apart. The two piece silver colored plastic connector moldings broke, exposing all the wires and for a few, the very poor soldering work. This one broke within a month. A slightly better one if connected up once and left alone might well last for a few years.
The fact that this is digital changes how we consider reliability. It either works or it doesn't. If it doesn't work, you'll be able to tell immediately. But what you won't know is if it will fail later even though it works now. When you see it working fine now, it might be an excellent cable and work forever, or it might be a piece of junk close to failing. It might work fine if connected once, then break when pulled out and plugged back in a few times. And the connections might corrode over time from humidity, or lose contact over time due to temperature changes.
But £100 or even $100 for a fancy cable is just not worth it. Something 1/5th of that might be right. Something 1/25th of that might be junk but then, if/when it does break, you can buy another.
The infection code can simply intercept all the I/O taking place and prevent the MBR from being cleaned, while also making it look like it has (by intercepting the reads, too). You need to boot from non-writable external media to be sure (non-writable just in case you accidentally boot into the hard drive, which will quickly infect any writable media). And if somehow this thing, or the next big virus/trojan, infects the BIOS by reflashing, even this is no good.
And there is one of the complex parts, the automated dependency detection. If they would just build the whole thing, you don't need that. Otherwise you need to know what to build, and what you don't need to build.
For very large projects, build everything can consume a lot of time. But most projects are smaller and should be able to build in under a minute.
The phone companies should be required to filter the caller ID info such that if any caller ID values that do not represent a phone number issued to that customer come through, the call will be rejected.
And that voltage needs to be one has a major source of batteries available as an auxiliary secondary power source. So make it be 12 volts to match all those car batteries out there. And it will work on my laptop instead of my brother's laptop:-)
No one (at least who knew the technical stuff) was physically present at the site at 3AM when the raid was conducted. So effectively, no one assisted the FBI. And, of course, FBI agents are not knowledgeable about how to figure out which servers have which sites, and would have to do their forensics to figure that out. Apparently an even bigger problem is that the way things were taken, servers that were not taken were left inoperable or unconnected (e.g. they unplugged stuff not exactly knowing what was where or tracing things down).
IMHO, law enforcement should be required to conduct these raids during business hours (to obtain identifying assistance from staff) unless there is a specific reason to believe that doing so would compromise the investigation (e.g. a very urgent need to move now, or that the ISP staff itself is involved and would hit a kill switch somewhere). And, maybe they thought this was just such a case.
The big question in your hosting company case is: how would they even know which equipment the data was on if no one assisted them?
And I hear that Google has a lot of Python running in-house already. But if fewer CPU cycle per function performed is the goal for low power mobile devices, why not just plain old C?
If you want bleeding edge GUI features and wrist cracking hand holding, then you are going to have to learn to keep moving along with the changes.
If you want solid, stable, time tested tools, see what's been around for 10 or 20 years and still kicking. Hint: that really is notepad, vi, and emacs (and minor clones). They made HTML, CSS, and Javascript in ASCII text for a reason.
Now, I just wish there was an option to fire up emacs for Slashdot posts.
Slashdot Mirror
... they break. Then both the 0's and the 1's cannot get through. Result: no sound, no picture. I had a very cheap HDMI cable from a low end retailer which simply fell apart. The two piece silver colored plastic connector moldings broke, exposing all the wires and for a few, the very poor soldering work. This one broke within a month. A slightly better one if connected up once and left alone might well last for a few years.
The fact that this is digital changes how we consider reliability. It either works or it doesn't. If it doesn't work, you'll be able to tell immediately. But what you won't know is if it will fail later even though it works now. When you see it working fine now, it might be an excellent cable and work forever, or it might be a piece of junk close to failing. It might work fine if connected once, then break when pulled out and plugged back in a few times. And the connections might corrode over time from humidity, or lose contact over time due to temperature changes.
But £100 or even $100 for a fancy cable is just not worth it. Something 1/5th of that might be right. Something 1/25th of that might be junk but then, if/when it does break, you can buy another.
... for my ad blocking filter system. So this means everyone on my LAN will be able to get around it and see the ads.
The infection code can simply intercept all the I/O taking place and prevent the MBR from being cleaned, while also making it look like it has (by intercepting the reads, too). You need to boot from non-writable external media to be sure (non-writable just in case you accidentally boot into the hard drive, which will quickly infect any writable media). And if somehow this thing, or the next big virus/trojan, infects the BIOS by reflashing, even this is no good.
And there is one of the complex parts, the automated dependency detection. If they would just build the whole thing, you don't need that. Otherwise you need to know what to build, and what you don't need to build. For very large projects, build everything can consume a lot of time. But most projects are smaller and should be able to build in under a minute.
I wonder how much of the complexity of these things is due to people wanting to be able to do an incremental build of just part of the whole thing.
... is email blast a resignation letter to everyone in the address book.
I blame the OS maker for not having it be the default and requiring the IT department to struggle with having to learn something new.
I've seen this one already.
The phone companies should be required to filter the caller ID info such that if any caller ID values that do not represent a phone number issued to that customer come through, the call will be rejected.
However, what should be against the law ...
Why should we allow the government to run our lives when corporations have proven they are quite capable of doing so?
Yeah, the Japanese don't need their voltage to be supported. Oh wait.
And that voltage needs to be one has a major source of batteries available as an auxiliary secondary power source. So make it be 12 volts to match all those car batteries out there. And it will work on my laptop instead of my brother's laptop :-)
No one (at least who knew the technical stuff) was physically present at the site at 3AM when the raid was conducted. So effectively, no one assisted the FBI. And, of course, FBI agents are not knowledgeable about how to figure out which servers have which sites, and would have to do their forensics to figure that out. Apparently an even bigger problem is that the way things were taken, servers that were not taken were left inoperable or unconnected (e.g. they unplugged stuff not exactly knowing what was where or tracing things down).
IMHO, law enforcement should be required to conduct these raids during business hours (to obtain identifying assistance from staff) unless there is a specific reason to believe that doing so would compromise the investigation (e.g. a very urgent need to move now, or that the ISP staff itself is involved and would hit a kill switch somewhere). And, maybe they thought this was just such a case.
The big question in your hosting company case is: how would they even know which equipment the data was on if no one assisted them?
They could use "goof" instead. But when has corporate every told the truth?
And I hear that Google has a lot of Python running in-house already. But if fewer CPU cycle per function performed is the goal for low power mobile devices, why not just plain old C?
So, then, does this set a record on /. for the oldest "old news" story?
Someone should be asking "How is this giving us a competitive edge when our competition is just using the same cloud?".
And I bet that was the CEO, too.
If you want bleeding edge GUI features and wrist cracking hand holding, then you are going to have to learn to keep moving along with the changes.
If you want solid, stable, time tested tools, see what's been around for 10 or 20 years and still kicking. Hint: that really is notepad, vi, and emacs (and minor clones). They made HTML, CSS, and Javascript in ASCII text for a reason.
Now, I just wish there was an option to fire up emacs for Slashdot posts.
Why do I envision an army of soldiers, all tightly aligned in square formation, wielding chairs?
Instead of phasing out nuclear power plants, why not just phase out incompetent managers.
There are benefits to IPv6-only. Among them, no RIAA or MPAA snoops (at least for a few years).
In the mean time, all the warez, tunez, moveez, and pr0n will be migrating to IPv6, where it can operate freely, unhindered by the lawyers.
Where are the models with SSD? Why did they stop making/shipping those?