Completely agree. You don't have to be able to bang out an OS, but man, if everybody just knew how to grep through some files or automatically run an SQL query, dump the results into an Excel file and email it to somebody, the world would be a better place.
Pick your poison. Get robbed by your coworkers or get robbed by your boss. You're still getting robbed. But I bet your coworkers will rob you less, given that they're being robbed by the same process.
Resistance was futile!
100 feet of buffer is inadequate. How the hell do you measure your AGL when you're flying? You either use a radar altimeter ($25K installed on an airplane worth $20K) or you use the baro altimeter, which has an acceptable calibration error, plus the local altimeter setting (atmospheric pressure) which has an error band, and there's error because you're not right over the reporting station.
Well, if you had a good GPS receiver and sufficiently detailed topographic maps on board you could also guesstimate AGL that way--but I agree that it's still a dubious and non-robust approach. And your radar altimeter doesn't have to run $25K if it only needs to work up to a few hundred feet and only be "hobbyist" or "drone" rated.
But really, forget measurement--that's probably not even the biggest problem. I suspect that it would be very technically challenging for these craft to physically maintain their permitted altitude. A good gust, an up- or down-draft, and your plus-or-minus 100 feet goes by in no time.
OTOH, my fascist firewall blocks blog posts such as Callaway's, so I really appreciate the hop through an unblocked source. I take it from context that article covers some stuff that isn't in the blog post, as well.
You're thinking of this as an either-or situation, when it really isn't. Hyperlinks are cheap. There's no reason for the summary not to clearly say, e.g."Here is the original blog post in its entirety, and here is an article which discusses some points from the blog post along with some other stuff." If they can't even manage that, then the link should at least clearly indicate that it isn't to the content described in the summary.
Instead, the Slashdot summary fails to link to the original blog post and implies misleadingly that the link in the summary actually does do so.
Oh, sure, I'm just saying it would be funny. Revenge for all the epithets
Bill Gates.
Replaces the front page of
Oh, you're absolutely right. I'm definitely not saying it would be impossible to hide a backdoor in an open core design. Absolutely could. Same thing with FOSS...just see the Underhanded C Competition.
But today you could have (and probably do have...) explicit backdoors in silicon, besides debugging interfaces, and you'd never know. With an open core design, you'd have to hide it.
They can if they believe that performer will incite violence, which I believe was their reasoning here as the performer is from one of the gangs involved in the violence. The concert was a fund raiser for a kid killed in the getaway after another gang shot one of Keef's gang members.
I don't think that's unreasonable.
If we're going to talk about Callaway's Points of Fail, and create a link in the Slashdot summary that *looks* like it takes you to that list, then perhaps there should actually be a link to the list.
Callaway's original Points of Fail blog post.
You know, instead of the usual Slashdot way of pointing to an article wrapper that talks briefly about some of the points and then eventually links to the real list.
I disagree. Saying "people couldn't understand the hardware" is the same as people saying "open source software is irrelevant because you can't understand the software."
Some people can. I have an electrical engineering degree and specialized in computer architecture in grad school. I could understand it. And just like anything else...it's not that hard when you know what you're looking at.
Eh. When laying out silicon, you generally use libraries of simple parts you chain together. You make a register once, and then you replicate it each place you need a register. A TON of those transistors are cache, which is the same pattern repeating over and over again.
I'm not saying there's anyone who's looked at every transistor, but there's probably somebody who's looked at the layout of a cache cell, a register, an ALU, standard multiplexers, etc.
You check out as the real KGIII. Or a very good KGIII Markov chain text generator.
CM and nearly all custom roms are immune and Lollipop is completely unaffected. Next time don't buy a carrier device.
Some of us don't have a choice, some of us still don't have a choice. Welcome to Canada.
Skeptical != cynical.
"Security is mostly a superstition. It does not exist in nature... Life is either a daring adventure or nothing." -- Helen Keller
