44 to 84 pounds is not the weight of the generator, it's the weight of the pendulum. The pendulum is whatever is in the backpack. If you already have 44+ pounds of books in the backpack, you're all set for the pendulum part.
I'd guess the generator itself is less than ten pounds, but the article didn't say.
the possibility that it was technology driving porn, and not the other way around?
On-line payment and DRM are about the only areas in which porn actually drove the innovation, if you want to call it that. Laser discs vs. DVD? Laser discs were too expensive compared to the cost of living, and the advantages over tape not well enough developed. Someone else mentioned the reality about VHS vs. Beta -- porn may have accelerated the selection, but it did not catalyze it.
Sure, there was undercurrent concerning porn, but I see pornography more as a parasite than a catalyst.
I assumed the list was a starting point and a reminder.
If you have a church, you ought to know whether or not you can trust their relief work.
In fact, if you attend regularly, you probably aren't here, but are on your way to help in whatever way your local group is helping.
If you are volunteering, volunteer with the group that you work best with. If you are donating, donate to the group you work best with. (If you're wondering why I'm here and not volunteering, I'm not in the country, so there isn't much I can do right now.)
Sounds to me like he did the best he could to get out of it, and finally found a way to save enough people enough embarassment that the incident can now go away.
They should have left them all outside where it was safe.
And why didn't they fly the supplies in before the hurricane passed through? Surely that would have saved time? Two jumbo jets should have been enough? Ten?
Well, since they didn't do that, they should have been running semis across the levy Monday morning. Checking for structural damage can wait, right?
Let's see. God doesn't do politics anymore, so you want the government to play God, right?
I have a better idea. If you're in the area, get your shovel and dig in. If you have some other chance to help, do so. Plenty of time to second guess the president/governor/mayor later.
anyway, I think they are some strategic issues involved, like where to drop how much of what, what the people there would do with it if they could keep it out of the water, and such. Likely, the problem is less with getting supplies to the general area and more with getting people organized to use the supplies constructively.
And getting people out of the water.
Sometimes it just is not possible to move fast enough to save everybody.
Two months? Not a chance. Two years, maybe. Long term plan? Leave it up to those who want to stick around and do the work of rebuilding.
I missed the Kobe earthquake by about 35 km. My wife did not. Two weeks was what it took to get her out of there. I still see the scars, although after about ten years it has mostly faded into the general ups and downs of day-to-day commerce.
New Orleans is a bit different. More space, more room to move things and people, but different stuff in the way, so to speak. And people behaving a bit more violently.
Gauging from what I saw in Kobe, I'd guess two months is what it will take to get conditions stable enough some of the people who live there can go back in and start cleaning up the mess.
It's analytic, not causal, and it's a test of potential for measured success in the current (or predicted future) environment.
It doesn't measure potential for unmeasured successes, it doesn't account for the possibility that the future may be drastically different than predicted, etc., etc.
Check the specs. All the vector stuff would have to be re-written for CELL. Without the re-write, all you have is a fast G3 and some hardware doing nothing.
Now, if you ask me, the re-write would be worth it. OpenGL, for instance, could be re-implemented on the CELL SPUs, and the OS could gain some nice benefits for the visual output. But that would still not be making very good use of the SPUs.
GarageBand and QuickTime (client) could also eventually get huge gains. But there's so much that would have to be done by hand first that Apple would have to have a chip with a full G5 core _and_ a complement of the SPUs in the high-end boxes to support the dev, with little visible gain for a year or two. Then, finally, Apple would be able to use one of the Sony PS3 chips effectively in a Mac Mini.
Making the SPUs fully useable in Mac OS X would likely require a complete new API, and that's going to hurt before it feels better.
Apple, when the iNTEL road map lead turns out to be mostly a paper lead yet again, would keep both iNTEL and PowerPC lines. And then start porting Darwin to ARM, CELL, and other available CPUs.
(Yeah, CELL would require a port. That's probably the point that Steve got sidetracked on. My guess is the discussions of re-writing for CELL produced a lot of complaints, and a lot of, "if we're going to have to do that, why not re-write for iNTEL?" Silly middle management.)
And in the best of all possible worlds, Linux on non-Apple PPC would push commodity mobo vendors to start focusing on alternative CPUs and alternative hardware. Then we could get out of the blasted rut we are in, where, in so many shops, you can't buy a project unless it includes a whole bunch of false standards.
You use MSExchange to format your letters? Form makes up for what's missing? You like HTML in your e-mail? Or were you talking about the overkill in using MSWord (or, as is common in Japan, MSExcel) to format your dead-tree letters?
Do you realize the trouble I go through to scrape useable information out of your letters? (MiSuse of XML.)
You use MSExcel to tally your spreadsheets? Do you realize how much overhead is in the average MSExcel spreadsheet? Do you realize how much time it takes me to keep the data extraction tools tuned to the constantly evolving content of those spreadsheets so I can get the tallies out of the spreadsheets and into the database? Do you realize the loops VB makes me jump through in the process?
Do you know how much time you spend keeping your database alive, accessible, and consistent when users of real databases don't think about it because the maintanence cost is not there?
Wait.
Was that a subconscious turn of phrase, keeping the database alive, accessible, and consistent, or are you just tweaking me?
Nope. It's a solution that mesmorizes the users into thinking it works. You know, like the joke about the drunk hunting for his wallet under the streetlamp because there's more light there?
How much time have I wasted with MSOffice documents, trying to get them to do something simple, just because it gets about 80% there and the boss thinks 80% is a hundred?
Microsoft follows the 80/20 rule. They sell you the eighty percent solution and deliver twenty percent of what you really need, plus a whole lot of bells and whistles to keep the bean counters happy and help look busy when your boss passes by.
But what you're mostly doing is fighting to make the software do what it's advertised to do, playing with the bells and whistles, or doing by hand what the other 20% of what the software actually did get 80% right, or undoing the stuff it did wrong.
Microsoft seems to write their software under the assumption that life is a context-free grammar.
The designers probably just included the MD5 just to scare the defendant. Whether or not that was their intent, they've proven themselves unqualified to be building these.
The red herring of the vulnerabilities aside, the only way you could really make a non-reputable speed camera work is to have the speedometer constantly broadcast the speed and a public key permanently assigned to the car (or perhaps the driver or the license plate?), and the camera would have to record the radar speed and the license plate (and the car, just to be sure) and hash all of it with the camera's private key, and hash it all again with the defendant's public key.
But that kind of gives the lie to the whole project, because the defendant would have to produce his private key to prove that the photos are not faked.
Ergo, this is requiring the defendant to testify against himself.
Thanks for pointing out the inherent weakness in trying to enforce software use limits with an EULA.
Of course, in spite of being sure they are distributing something, we don't know for sure that they are violating the GPL or any of the other licenses they might be using, but if we could get them to hold still long enough for pre-suit legal maneuvering, well, uhmmm, what then?
Slashdot Mirror
I could be wrong, but that's the way I read it.
44 to 84 pounds is not the weight of the generator, it's the weight of the pendulum. The pendulum is whatever is in the backpack. If you already have 44+ pounds of books in the backpack, you're all set for the pendulum part.
I'd guess the generator itself is less than ten pounds, but the article didn't say.
Read nothing in your post that I can see as being persuasive.
You did swear a lot.
I'm sure management has already asked those questions and more, maybe even complete with expletives.
I've got an OSS project that needs funds and programmers.
the possibility that it was technology driving porn, and not the other way around?
On-line payment and DRM are about the only areas in which porn actually drove the innovation, if you want to call it that. Laser discs vs. DVD? Laser discs were too expensive compared to the cost of living, and the advantages over tape not well enough developed. Someone else mentioned the reality about VHS vs. Beta -- porn may have accelerated the selection, but it did not catalyze it.
Sure, there was undercurrent concerning porn, but I see pornography more as a parasite than a catalyst.
I assumed the list was a starting point and a reminder.
If you have a church, you ought to know whether or not you can trust their relief work.
In fact, if you attend regularly, you probably aren't here, but are on your way to help in whatever way your local group is helping.
If you are volunteering, volunteer with the group that you work best with. If you are donating, donate to the group you work best with. (If you're wondering why I'm here and not volunteering, I'm not in the country, so there isn't much I can do right now.)
Sounds to me like he did the best he could to get out of it, and finally found a way to save enough people enough embarassment that the incident can now go away.
Maybe they expect New Orleans to be a big campground for a couple of weeks? A big catered campground? Maybe a little damp?
Probably they're in shock and aren't thinking clearly, but since they can't be all evacuated in an hour, getting supplies in is important.
They should have left them all outside where it was safe.
And why didn't they fly the supplies in before the hurricane passed through? Surely that would have saved time? Two jumbo jets should have been enough? Ten?
Well, since they didn't do that, they should have been running semis across the levy Monday morning. Checking for structural damage can wait, right?
Let's see. God doesn't do politics anymore, so you want the government to play God, right?
I have a better idea. If you're in the area, get your shovel and dig in. If you have some other chance to help, do so. Plenty of time to second guess the president/governor/mayor later.
Drop food from airplanes?
...
Reminds me of the WKRP episode where
anyway, I think they are some strategic issues involved, like where to drop how much of what, what the people there would do with it if they could keep it out of the water, and such. Likely, the problem is less with getting supplies to the general area and more with getting people organized to use the supplies constructively.
And getting people out of the water.
Sometimes it just is not possible to move fast enough to save everybody.
Two months? Not a chance. Two years, maybe. Long term plan? Leave it up to those who want to stick around and do the work of rebuilding.
I missed the Kobe earthquake by about 35 km. My wife did not. Two weeks was what it took to get her out of there. I still see the scars, although after about ten years it has mostly faded into the general ups and downs of day-to-day commerce.
New Orleans is a bit different. More space, more room to move things and people, but different stuff in the way, so to speak. And people behaving a bit more violently.
Gauging from what I saw in Kobe, I'd guess two months is what it will take to get conditions stable enough some of the people who live there can go back in and start cleaning up the mess.
The world is not a safe place.
I mean, like, get WITH IT, man. Freedom is soooooo passe.
Is that what you're saying?
No, the government isn't perfect. You want to take your turn trying to fix the world's problems now?
stuff --> staff /.
this --> this thread on
So I doubt they'll see a need to publish it in Engrish.
Unless one of their stuff notices this and figures damage control is necessary.
For those who, like me, prefer reading intelligible Japanese over machine translation, here.
Once upon a time I remembered that %2f was slash and %3f was question mark, etc.
are a much healthier source of caffiend.
/. to stay awayke, myself.)
(I read
That's kind of like the whole point.
It's analytic, not causal, and it's a test of potential for measured success in the current (or predicted future) environment.
It doesn't measure potential for unmeasured successes, it doesn't account for the possibility that the future may be drastically different than predicted, etc., etc.
and it's a headline on /.
Check the specs. All the vector stuff would have to be re-written for CELL. Without the re-write, all you have is a fast G3 and some hardware doing nothing.
Now, if you ask me, the re-write would be worth it. OpenGL, for instance, could be re-implemented on the CELL SPUs, and the OS could gain some nice benefits for the visual output. But that would still not be making very good use of the SPUs.
GarageBand and QuickTime (client) could also eventually get huge gains. But there's so much that would have to be done by hand first that Apple would have to have a chip with a full G5 core _and_ a complement of the SPUs in the high-end boxes to support the dev, with little visible gain for a year or two. Then, finally, Apple would be able to use one of the Sony PS3 chips effectively in a Mac Mini.
Making the SPUs fully useable in Mac OS X would likely require a complete new API, and that's going to hurt before it feels better.
And how does one convince the PHBs at Adobe?
Apple, when the iNTEL road map lead turns out to be mostly a paper lead yet again, would keep both iNTEL and PowerPC lines. And then start porting Darwin to ARM, CELL, and other available CPUs.
(Yeah, CELL would require a port. That's probably the point that Steve got sidetracked on. My guess is the discussions of re-writing for CELL produced a lot of complaints, and a lot of, "if we're going to have to do that, why not re-write for iNTEL?" Silly middle management.)
And in the best of all possible worlds, Linux on non-Apple PPC would push commodity mobo vendors to start focusing on alternative CPUs and alternative hardware. Then we could get out of the blasted rut we are in, where, in so many shops, you can't buy a project unless it includes a whole bunch of false standards.
You're my boss?
You use MSExchange to format your letters? Form makes up for what's missing? You like HTML in your e-mail? Or were you talking about the overkill in using MSWord (or, as is common in Japan, MSExcel) to format your dead-tree letters?
Do you realize the trouble I go through to scrape useable information out of your letters? (MiSuse of XML.)
You use MSExcel to tally your spreadsheets? Do you realize how much overhead is in the average MSExcel spreadsheet? Do you realize how much time it takes me to keep the data extraction tools tuned to the constantly evolving content of those spreadsheets so I can get the tallies out of the spreadsheets and into the database? Do you realize the loops VB makes me jump through in the process?
Do you know how much time you spend keeping your database alive, accessible, and consistent when users of real databases don't think about it because the maintanence cost is not there?
Wait.
Was that a subconscious turn of phrase, keeping the database alive, accessible, and consistent, or are you just tweaking me?
I think you're just tweaking me.
Nope. It's a solution that mesmorizes the users into thinking it works. You know, like the joke about the drunk hunting for his wallet under the streetlamp because there's more light there?
How much time have I wasted with MSOffice documents, trying to get them to do something simple, just because it gets about 80% there and the boss thinks 80% is a hundred?
jes kiddin
Microsoft follows the 80/20 rule. They sell you the eighty percent solution and deliver twenty percent of what you really need, plus a whole lot of bells and whistles to keep the bean counters happy and help look busy when your boss passes by.
But what you're mostly doing is fighting to make the software do what it's advertised to do, playing with the bells and whistles, or doing by hand what the other 20% of what the software actually did get 80% right, or undoing the stuff it did wrong.
Microsoft seems to write their software under the assumption that life is a context-free grammar.
Would there be room to build houses in the shade?
Apparently, including the lawyer.
And perhaps not including the judge.
The designers probably just included the MD5 just to scare the defendant. Whether or not that was their intent, they've proven themselves unqualified to be building these.
The red herring of the vulnerabilities aside, the only way you could really make a non-reputable speed camera work is to have the speedometer constantly broadcast the speed and a public key permanently assigned to the car (or perhaps the driver or the license plate?), and the camera would have to record the radar speed and the license plate (and the car, just to be sure) and hash all of it with the camera's private key, and hash it all again with the defendant's public key.
But that kind of gives the lie to the whole project, because the defendant would have to produce his private key to prove that the photos are not faked.
Ergo, this is requiring the defendant to testify against himself.
Thanks for pointing out the inherent weakness in trying to enforce software use limits with an EULA.
Of course, in spite of being sure they are distributing something, we don't know for sure that they are violating the GPL or any of the other licenses they might be using, but if we could get them to hold still long enough for pre-suit legal maneuvering, well, uhmmm, what then?