Carrier Pidgeon's only a layer 2 protocol, which makes absolutely no guarantees on delivery. I'm assuming you're talking about running IP over Carrier Pidgeon, and then you'd still need TCP on top of that,
That's not what he (she?) was saying. He was saying that if Jimbo says there's a 1% chance of the tire failing, and Jimbo's wrong 50% of the time (and that him being wrong is independent of the tire failing) and that we don't know what the chances of the tire failing are if he is wrong, then the maximum likelihood of the tire failing are at worst 50.5%. At worst.
It could be as low as.5% to the best of our knowledge (if we know that whenever he's wrong, the tire never fails). But it can't be worse than 50.5%, because there's no way that the tire fails more than 100% of the time when he's wrong.
Probability is not the same as maximum likelihood. Nor are either of them the same as knowing whether the event will actually happen or not. Probability is an estimate. Maximum likelihood is a worst-case estimate (in this case, where we define bad to be high probability). Knowing whether or not the thing actually happens is voodoo.
I go to school here, and I have to say that I'm pretty sure the increased energy usage isn't from us having DST, it's from us being in the wrong time zone. It'd be interesting to see what things are like in Illinois (next time zone over, but still pretty close, sun-wise).
One of the things I personally am the most excited about is the ability to do function-level optimization in 4.4. Last year, I had a project that required me to have compiled code be as fast as possible, but you could only submit one source file and no Makefiles, which would be compiled with no arguments, optimizations, etc.. With this, I could throw the optimizations straight into the code, instead of having to compile with optimizations, taking the assembly, throwing that into a wrapper C file, and hoping the code was tested on the same architecture.
Hell, fire's 'alive' by that definition. As long as it's got fuel, it metabolizes fuel, it physically grows as time goes on, and often, one flame will split into two when the fuel in the middle runs out. Yes, I know there's more to it than that, but I'm just pointing out that we've gotta be careful about how we define life, or else we run into a few problems we aren't anticipating.
Unfortunately, there are a number of problems with LSB. One of the worst problems is that of Fortran. Fortran libraries aren't in LSB, and most distros don't distribute them by default. (Ones I've tested: Fedora, RHEL, Debian, and Ubuntu). Sure, everyone knows and loves C, but especially a lot of scientific computing applications that are still actively being used and developed today, were written in Fortran, and it would be more effort than the developers are willing to put in to port them to C. But LSB complains about Fortran that there aren't enough active developers of it (are there any? is there even a 4.0 version of g77?) and that not enough major distros are throwing it in by default. The other major problem is that of simply not including Debian, on account of not having a compatible packaging system (which, by the way, is more widespread than RPM, arguably more powerful than RPM, and precedes it).
Ok, first of all, you're confusing 'hacks' with 'cracks.' People 'hack' hardware, software, etc., on their own personal devices to make them do what they want. So of course people will hack anything, or try to. Everything you listed has indeed been hacked. Cracking, however is a different matter. People 'crack' other people's hardware, software, or devices to make them do what the cracker wants without the owner knowing. The PSP has not been 'cracked.' The iPhone has not been 'cracked.' The Xbox has not been 'cracked.'
Macs have been hacked, and cracked, convincingly, as sibling mentions.
I agree that security, or lack thereof is not directly proportional to market share. I'm just saying that if market share is small, security is irrelevant. Apple has gotten used to it being irrelevant.
On another, slightly off-topic note, it's people like you who give Linux and hackers a bad name. Stop it.
On another, slightly more off-topic note, I'm writing this from my new (jailbroken) iPhone, which I am pleased of.
apple was never secure. It was just unused. The exact same thing is going ATM with their X server. Not so much a security flaw (though it might be) as much as a major bug. If you send too many events at once (not insane amounts, just a lot) it simply crashed, bringing down all the X apps with it. Upstream was fixed over a year ago, they just refuse to roll out an update. I guess it's an attempt to make debs port to coco/carbon/whatever-it's-called, but for some of us, that's just not an option. More specifically, it's a program developed by part of a university bioinformatics lab, and we just don't have the manpower or the grant support to do it. So we're either stuck with only supporting Linux, trying to find a wrkaround, or just ignoring it and hope it doesn't happen to often. The last option is what we ended up choosing.
Wrong, wrong, wrong! The TSA IS a part of the government. It's part of the DHS. Sure, the airlines can ask for your ID, and bar you from flying if you don't show it, but the TSA CANNOT. And if it weren't a part of the government, it could ask for your ID, but then it would have no authority to prevent you from flying if you don't. This is exactly what the fourth amendment was designed for.
Not only that, but the constitution provides protection from unreasonable search and seizure by the fourth amendment and explicitly includes papers as part of the search. Yes, that's in public too ("...secure in their persons, houses, papers, and effects..."). They can't ask for ID unless they've got a warrant, probable cause, or you've already recently committed a crime. And no, refusing to show ID CANNOT be deemed 'probable cause'.
Hell, my university's got a whole frickin' School of Management. My roommate, even, is trying to major in 'Managerial Accounting.' I say trying, because he can't manage to keep a 2.75, so he's slowly deciding to switch to Economics. And even during his 2nd year management courses, I could essentially do his homework for him, by merely skimming the assigned chapter. And the professors have the nerve to teach 'Word' and 'Excel' and 'Access,' instead of word processing and spreadsheets and databases. It's nuts, because the students don't actually learn anything of value.
Google does have a competitor. It's called "Checkout." However, it sucks, because no one uses it, and no one uses it because it sucks. And I'm sure they shave just as much off the top as Paypal does.
That's +16GB Flash ROM, not +16GB SRAM (or DRAM? I'm not sure which the iPhone uses). They're both called memory, but using a Flash ROM as your main memory, no matter how much of it you had, well, you just plain wouldn't want to do it. Imagine Vista on 1MB of RAM.
Unless my irony detector is broken, in which case you already knew that.
Except what you're saying is that they'll be shaping everything, evenly, regardless of format. And if you're shaping everything evenly, it ceases being shaping, and becomes straight-up throttling. Everyone else does that already.
Slashdot Mirror
Carrier Pidgeon's only a layer 2 protocol, which makes absolutely no guarantees on delivery. I'm assuming you're talking about running IP over Carrier Pidgeon, and then you'd still need TCP on top of that,
FttB? (Fiber to the Brain)
That's not what he (she?) was saying. He was saying that if Jimbo says there's a 1% chance of the tire failing, and Jimbo's wrong 50% of the time (and that him being wrong is independent of the tire failing) and that we don't know what the chances of the tire failing are if he is wrong, then the maximum likelihood of the tire failing are at worst 50.5%. At worst.
.5% to the best of our knowledge (if we know that whenever he's wrong, the tire never fails). But it can't be worse than 50.5%, because there's no way that the tire fails more than 100% of the time when he's wrong.
It could be as low as
Probability is not the same as maximum likelihood. Nor are either of them the same as knowing whether the event will actually happen or not. Probability is an estimate. Maximum likelihood is a worst-case estimate (in this case, where we define bad to be high probability). Knowing whether or not the thing actually happens is voodoo.
Hooray for bootstrapping! Us computer engineers finally have some useful lessons to contribute to society!
I, for one, welcome our new artificially intelligent overlords.
I go to school here, and I have to say that I'm pretty sure the increased energy usage isn't from us having DST, it's from us being in the wrong time zone. It'd be interesting to see what things are like in Illinois (next time zone over, but still pretty close, sun-wise).
One of the things I personally am the most excited about is the ability to do function-level optimization in 4.4. Last year, I had a project that required me to have compiled code be as fast as possible, but you could only submit one source file and no Makefiles, which would be compiled with no arguments, optimizations, etc.. With this, I could throw the optimizations straight into the code, instead of having to compile with optimizations, taking the assembly, throwing that into a wrapper C file, and hoping the code was tested on the same architecture.
It's scripting, Jim, but not as we know it. The "scripting" in LBP is all physics-based.
You know, it might, but if it did, it probably wouldn't get pulled for those.
If they tacked on a year to the product name, they'd be bound to that date and would never hear the end of it when it's late.
That's what I thought they were doing...until I realized 2007's been over for a while now.
Hell, fire's 'alive' by that definition. As long as it's got fuel, it metabolizes fuel, it physically grows as time goes on, and often, one flame will split into two when the fuel in the middle runs out. Yes, I know there's more to it than that, but I'm just pointing out that we've gotta be careful about how we define life, or else we run into a few problems we aren't anticipating.
Unfortunately, there are a number of problems with LSB. One of the worst problems is that of Fortran. Fortran libraries aren't in LSB, and most distros don't distribute them by default. (Ones I've tested: Fedora, RHEL, Debian, and Ubuntu). Sure, everyone knows and loves C, but especially a lot of scientific computing applications that are still actively being used and developed today, were written in Fortran, and it would be more effort than the developers are willing to put in to port them to C. But LSB complains about Fortran that there aren't enough active developers of it (are there any? is there even a 4.0 version of g77?) and that not enough major distros are throwing it in by default. The other major problem is that of simply not including Debian, on account of not having a compatible packaging system (which, by the way, is more widespread than RPM, arguably more powerful than RPM, and precedes it).
Actually, that's perfectly correct grammar, assuming 'known' was a typo and was supposed to be 'knock' (a perfectly valid assumption). </-Wpedantic>
I dunno about you, I'm just anti-Symantec.
Ok, first of all, you're confusing 'hacks' with 'cracks.' People 'hack' hardware, software, etc., on their own personal devices to make them do what they want. So of course people will hack anything, or try to. Everything you listed has indeed been hacked. Cracking, however is a different matter. People 'crack' other people's hardware, software, or devices to make them do what the cracker wants without the owner knowing. The PSP has not been 'cracked.' The iPhone has not been 'cracked.' The Xbox has not been 'cracked.' Macs have been hacked, and cracked, convincingly, as sibling mentions. I agree that security, or lack thereof is not directly proportional to market share. I'm just saying that if market share is small, security is irrelevant. Apple has gotten used to it being irrelevant. On another, slightly off-topic note, it's people like you who give Linux and hackers a bad name. Stop it. On another, slightly more off-topic note, I'm writing this from my new (jailbroken) iPhone, which I am pleased of.
apple was never secure. It was just unused. The exact same thing is going ATM with their X server. Not so much a security flaw (though it might be) as much as a major bug. If you send too many events at once (not insane amounts, just a lot) it simply crashed, bringing down all the X apps with it. Upstream was fixed over a year ago, they just refuse to roll out an update. I guess it's an attempt to make debs port to coco/carbon/whatever-it's-called, but for some of us, that's just not an option. More specifically, it's a program developed by part of a university bioinformatics lab, and we just don't have the manpower or the grant support to do it. So we're either stuck with only supporting Linux, trying to find a wrkaround, or just ignoring it and hope it doesn't happen to often. The last option is what we ended up choosing.
I dunno about you guys, but I recommend re-barment. Shoving a length of steel re-bar through his body sounds pretty good to me...
Wrong, wrong, wrong! The TSA IS a part of the government. It's part of the DHS. Sure, the airlines can ask for your ID, and bar you from flying if you don't show it, but the TSA CANNOT. And if it weren't a part of the government, it could ask for your ID, but then it would have no authority to prevent you from flying if you don't. This is exactly what the fourth amendment was designed for.
Not only that, but the constitution provides protection from unreasonable search and seizure by the fourth amendment and explicitly includes papers as part of the search. Yes, that's in public too ("...secure in their persons, houses, papers, and effects..."). They can't ask for ID unless they've got a warrant, probable cause, or you've already recently committed a crime. And no, refusing to show ID CANNOT be deemed 'probable cause'.
Hell, my university's got a whole frickin' School of Management. My roommate, even, is trying to major in 'Managerial Accounting.' I say trying, because he can't manage to keep a 2.75, so he's slowly deciding to switch to Economics. And even during his 2nd year management courses, I could essentially do his homework for him, by merely skimming the assigned chapter. And the professors have the nerve to teach 'Word' and 'Excel' and 'Access,' instead of word processing and spreadsheets and databases. It's nuts, because the students don't actually learn anything of value.
When will it stop?!?!?
Google does have a competitor. It's called "Checkout." However, it sucks, because no one uses it, and no one uses it because it sucks. And I'm sure they shave just as much off the top as Paypal does.
Yes, and people voted for Bush. The second time around.
That's +16GB Flash ROM, not +16GB SRAM (or DRAM? I'm not sure which the iPhone uses). They're both called memory, but using a Flash ROM as your main memory, no matter how much of it you had, well, you just plain wouldn't want to do it. Imagine Vista on 1MB of RAM. Unless my irony detector is broken, in which case you already knew that.
Except what you're saying is that they'll be shaping everything, evenly, regardless of format. And if you're shaping everything evenly, it ceases being shaping, and becomes straight-up throttling. Everyone else does that already.