I'd most definitely like to have that information. I'm always scanning for pedestrian timers so I'd definitely use it. However, the person that hit you was either not paying attention, tailgating, or both. From a defensive driving posture that info may have helped, but, as an alternative defensive action, I'd probably have just kept going rather than slam my brakes.
I would make the claim that perhaps you were speeding to need to slam the brakes in the first place, but there's been enough discussion of yellow light timers here that it may very well have been timed to shortly allowing benefit of the doubt. If that's the case I'd make the claim that the issue to fix is the yellow light timing and not work arounds like this to deal with poor timing.
To sum up, this information shouldn't be needed to prevent being rear ended at an interestion with a light turning red, and I don't think the addition of it would help under proper conditions. The original stated use, efficiency gains, remains the most sensible.
The guy behind you couldn't manage to pay enough attention to avoid colliding with vehicle directly in front of him. What makes you think he has the mental capacity to plan ahead when the planning process requires actual thought? It saddens me, but I don't think technical solutions will matter here so long as people like that are in total control of the vehicle.
How is it a filesystem in the unix philsophy? It's monolithic in the worst possible way; a clumsy mess of layering violations. One analogy would be if someone said "http would be so much better if it wasn't for those pesky tcp, ip, and ethernet layers!"
I remain bitter that all of that work into advanced data protection, volume management, and efficiency features was wasted on a single filesystem instead of placed in device mapper where they belong. Then ext4 could have useful features such dedupe, load balancing, compression, etc. Hell, if proper layer constraints and software design were used FAT16 could have these features!
Shame on ZFS, shame on BTRFS, and shame on the community for supporting these abominations.
Ctrl-A to select all Triple Click The ability to select text from e.g. labels to copy at all.. Proper ordering of widgets for tab Click radio button/check box label
Etc.
If applications could just get the basics right it'd go a long way.
Which is interesting considering ScreenOS has among the most annoying CLIs I've ever used. However, the web interface is so freaking good that I don't care.
I'm going to miss it when Juniper finally kills it..
You just described the evil maid attack. There is a technology designed to protect against that. It's very common in laptops, but hard to find in desktop boards./. inexplicably hates it. It's that magic TPM chip. Boot time chain of trust is a well researched, well understood, and, when ignorance isn't pushing it out of markets like desktops, a mostly solved problem.
There are two good reasons to care about "real" Mac server hardware.
With the lack of proper Mac server hardware and the draconian EULA of OS X Apple has successfully avoided collecting untold sums of cash in licensing fees for VDI. It's embarassing. All they would need to do is either produce the hardware or allow virtualization of their desktop and server OS on non Apple hardware. After that some on their knees begging to Citrix and VMware would help to expedite support.
I've been surprised by the lack of reference of proper error checked data paths so far in these comments. I'm continually saddened by ever increasing aggressiveness in clocks and density of RAM in consumer level systems while stubbornly refusing to implement ECC. Many people are even hostile to the idea as if ECC RAM is somehow tainted.
This article points out something else I'd not even considered. A scenario where lack of ECC on a self healing file system can amplify a RAM failure to a catastrophic degree making such filesystems even riskier to run on consumer grade systems.
In my case it's because my job is to talk to computers, not people. I don't need or want to hear every co workers phone call, every impromptu in the middle of the hall way meeting, etc. It's only a distraction and absolutely destroys productivity.
Both cited examples, tailgaters and people who cut others, do not have "rapid acceleration" as a requisite. Tailgating is more frequently brought on by stupidity, obliviousness, and a complete failure to comprehend newtonian mechanics and human reaction time. Most people who tailgate aren't even aware they're doing it.
Cutting a person off merely requires proximity and a complete lack of empathy and/or attention.
I'll accelerate fast simply so I can stop changing gears and cruise. I won't tailgate you or cut you off.
Wow I'd love to be able to consider $1200 a year to be crazy expensive.. must be nice being you. Clearly this thing will only confirm what the insurance company already knows based purely on my credit score.
Slamming the brakes also assumes the person behind you isn't too close and is paying attention, and the guy behind him, the guy behind him, so on and so forth. Even if you avoid the pile up you just caused a traffic jam. If you can avoid the collision by temporarily speeding up it's much safer to do so.
Also, driving period has the potential to become dangerous. Delcaring passing a slower driver as a dangerous manuever is absurd.
The general point remains. These devices lack situational context, and a design by committee formula for what consistutes safe based on this data is likely to be stupendously flawed. I tend to equate it to the absurdity that IT regulations tend to produce such as the hidden essid requirement of PCI-DSS.
Conciseness, brevity, clarity, succinctness, accuracy, precision, etc.
You use paragraphs of sixth grader terminology to express a complex idea then create a single word to express that same idea in the future. A word doesn't even need to encode a complex idea. It can, in addition to or instead, encode context or connotation. "Big words" do not exist solely to boost egos.
Unless we regulate them. Corporate entities have only the rights we the people wish to bestow and allow. This smells very much like a common carrier type issue.
I can't wait. Trying to find TPM support for my last build proved too difficult so I had to drop that from my "nice to have" list. I'd like to thank Microsoft for finally pushing manufacturers to use and support these chips. The capabilities these chips provide for secure storage of cryptographic keys, hardware validation, and boot time chain of trust are immensly useful for securing data.
That's what they do, you know.. store and assist with generating crypto keys and perform platform validation so that you can, e.g., validate that your boot loader is not tampered with before it will release those keys. Hardware support for protecting against evil maid and transparent full disk encryption. That's such a bummer! Why would anyone want that?!
10Mbps 1080p doesn't qualify here? Finding that kind of quality through piracy is extraordinarily difficult.
There isn't a single service in the United States or almost anywhere that allows real-time, on demand programming without advertisements.
Well, ignoring Netflix, there's vudu.com which I use frequently. They even support play later downloading. There's also Amazon instant streaming, but I avoid that due to the sub par quality vs Netflix.
Between Netflix and VUDU I can get higher quality videos more easily than any piracy avenue.
Interestingly enough, the show this article is about is not on either service. I've never heard of it because of that, and my give a shit is precisely 0. For the obsessive "Must See Now!" crowd that can't wait for it to be available on such services or find something equally entertaining that is available now the gap still exists. While I have no sympathy for that mentality as I learned long ago that it is mostly a waste of energy and generally unhealthy, I will agree it's a giant gaping hole in the market. All there is is Hulu, which has ads, with a monthly payment, and half the content won't work on appliances designed for televisions.
Slashdot Mirror
I'd most definitely like to have that information. I'm always scanning for pedestrian timers so I'd definitely use it. However, the person that hit you was either not paying attention, tailgating, or both. From a defensive driving posture that info may have helped, but, as an alternative defensive action, I'd probably have just kept going rather than slam my brakes.
I would make the claim that perhaps you were speeding to need to slam the brakes in the first place, but there's been enough discussion of yellow light timers here that it may very well have been timed to shortly allowing benefit of the doubt. If that's the case I'd make the claim that the issue to fix is the yellow light timing and not work arounds like this to deal with poor timing.
To sum up, this information shouldn't be needed to prevent being rear ended at an interestion with a light turning red, and I don't think the addition of it would help under proper conditions. The original stated use, efficiency gains, remains the most sensible.
The guy behind you couldn't manage to pay enough attention to avoid colliding with vehicle directly in front of him. What makes you think he has the mental capacity to plan ahead when the planning process requires actual thought? It saddens me, but I don't think technical solutions will matter here so long as people like that are in total control of the vehicle.
How is it a filesystem in the unix philsophy? It's monolithic in the worst possible way; a clumsy mess of layering violations. One analogy would be if someone said "http would be so much better if it wasn't for those pesky tcp, ip, and ethernet layers!"
I remain bitter that all of that work into advanced data protection, volume management, and efficiency features was wasted on a single filesystem instead of placed in device mapper where they belong. Then ext4 could have useful features such dedupe, load balancing, compression, etc. Hell, if proper layer constraints and software design were used FAT16 could have these features!
Shame on ZFS, shame on BTRFS, and shame on the community for supporting these abominations.
I find the little things often neglected such as:
Ctrl-A to select all
Triple Click
The ability to select text from e.g. labels to copy at all..
Proper ordering of widgets for tab
Click radio button/check box label
Etc.
If applications could just get the basics right it'd go a long way.
Which is interesting considering ScreenOS has among the most annoying CLIs I've ever used. However, the web interface is so freaking good that I don't care.
I'm going to miss it when Juniper finally kills it..
You just described the evil maid attack. There is a technology designed to protect against that. It's very common in laptops, but hard to find in desktop boards. /. inexplicably hates it. It's that magic TPM chip. Boot time chain of trust is a well researched, well understood, and, when ignorance isn't pushing it out of markets like desktops, a mostly solved problem.
So...
cat password_file /path/to/my_super_secret_key | gpg --batch --passphrase-fd 0 -d password_file
vs
cat
The difference just doesn't seem that pronounced to me.
TFA discusses whether or not the universe is holographic not if it's simulated.
There are two good reasons to care about "real" Mac server hardware.
With the lack of proper Mac server hardware and the draconian EULA of OS X Apple has successfully avoided collecting untold sums of cash in licensing fees for VDI. It's embarassing. All they would need to do is either produce the hardware or allow virtualization of their desktop and server OS on non Apple hardware. After that some on their knees begging to Citrix and VMware would help to expedite support.
The second is build farms. One of the most embarassing things I've ever had to do is _rack_ a cluster of mac mini's. It's so, so sad: http://mk1manufacturing.com/store/cart.php?m=product_list&c=17.
I've been surprised by the lack of reference of proper error checked data paths so far in these comments. I'm continually saddened by ever increasing aggressiveness in clocks and density of RAM in consumer level systems while stubbornly refusing to implement ECC. Many people are even hostile to the idea as if ECC RAM is somehow tainted.
This article points out something else I'd not even considered. A scenario where lack of ECC on a self healing file system can amplify a RAM failure to a catastrophic degree making such filesystems even riskier to run on consumer grade systems.
Thank you for sharing.
In my case it's because my job is to talk to computers, not people. I don't need or want to hear every co workers phone call, every impromptu in the middle of the hall way meeting, etc. It's only a distraction and absolutely destroys productivity.
You're discussing different behaviors of the same group of people.
In my experience most people haven't even figured out that going faster than the car you're passing is a requisite to pass... You expect too much.
It wasn't wasted. It achieved the exact purpose it was used for.. getting up to speed quickly!
Both cited examples, tailgaters and people who cut others, do not have "rapid acceleration" as a requisite. Tailgating is more frequently brought on by stupidity, obliviousness, and a complete failure to comprehend newtonian mechanics and human reaction time. Most people who tailgate aren't even aware they're doing it.
Cutting a person off merely requires proximity and a complete lack of empathy and/or attention.
I'll accelerate fast simply so I can stop changing gears and cruise. I won't tailgate you or cut you off.
I fail to even see correlation.
Wow I'd love to be able to consider $1200 a year to be crazy expensive.. must be nice being you. Clearly this thing will only confirm what the insurance company already knows based purely on my credit score.
Slamming the brakes also assumes the person behind you isn't too close and is paying attention, and the guy behind him, the guy behind him, so on and so forth. Even if you avoid the pile up you just caused a traffic jam. If you can avoid the collision by temporarily speeding up it's much safer to do so.
Also, driving period has the potential to become dangerous. Delcaring passing a slower driver as a dangerous manuever is absurd.
The general point remains. These devices lack situational context, and a design by committee formula for what consistutes safe based on this data is likely to be stupendously flawed. I tend to equate it to the absurdity that IT regulations tend to produce such as the hidden essid requirement of PCI-DSS.
Conciseness, brevity, clarity, succinctness, accuracy, precision, etc.
You use paragraphs of sixth grader terminology to express a complex idea then create a single word to express that same idea in the future. A word doesn't even need to encode a complex idea. It can, in addition to or instead, encode context or connotation. "Big words" do not exist solely to boost egos.
"employment is idiotic and has become a modern-day form of feudalism" is sufficient. Throwing in employment dependent health care is just icing.
Indeed, and none of this happens at all with private insurers. Nobody has ever been denied a life saving procedure by an insurance company .. ever!
Unless we regulate them. Corporate entities have only the rights we the people wish to bestow and allow. This smells very much like a common carrier type issue.
There are no shortage of unskilled jobs to work
You must not be paying attention. There's been a shortage of jobs for a few years now. Started around '08? Called a recession? Ringing any bells?
I can't wait. Trying to find TPM support for my last build proved too difficult so I had to drop that from my "nice to have" list. I'd like to thank Microsoft for finally pushing manufacturers to use and support these chips. The capabilities these chips provide for secure storage of cryptographic keys, hardware validation, and boot time chain of trust are immensly useful for securing data.
That's what they do, you know.. store and assist with generating crypto keys and perform platform validation so that you can, e.g., validate that your boot loader is not tampered with before it will release those keys. Hardware support for protecting against evil maid and transparent full disk encryption. That's such a bummer! Why would anyone want that?!
Even Netflix doesn't offer true HD streaming
10Mbps 1080p doesn't qualify here? Finding that kind of quality through piracy is extraordinarily difficult.
There isn't a single service in the United States or almost anywhere that allows real-time, on demand programming without advertisements.
Well, ignoring Netflix, there's vudu.com which I use frequently. They even support play later downloading. There's also Amazon instant streaming, but I avoid that due to the sub par quality vs Netflix.
Between Netflix and VUDU I can get higher quality videos more easily than any piracy avenue.
Interestingly enough, the show this article is about is not on either service. I've never heard of it because of that, and my give a shit is precisely 0. For the obsessive "Must See Now!" crowd that can't wait for it to be available on such services or find something equally entertaining that is available now the gap still exists. While I have no sympathy for that mentality as I learned long ago that it is mostly a waste of energy and generally unhealthy, I will agree it's a giant gaping hole in the market. All there is is Hulu, which has ads, with a monthly payment, and half the content won't work on appliances designed for televisions.
Screw Hulu
So, in other words, doesn't work on Linux..