But that meeting, ideally, should be geeks meeting with other geeks, and hammering out interface specs.
There should not be sales, marketing, HR, upper management, or any other irrelevant staff involved. Only the project leader/manager, and the geeks in question.
If the project manager doesn't relate to the geeks (s)he's managing, then they're not the right person for the job.
And geeks can sit and talk about technology with other geeks to the wee hours of the morning. Just ask my wife. She'll verify that.
(OMGLOLWTFBBQ!!! A/.er with a wife!!?!?!?) Yeah... and two kids. So you can figure out what we do with our evenings.....
So trucks in America don't use chains in the winter? What do they use? If they use chains it's perfectly relevant.
A lot of places in the south of the USA don't have "winter" per se. Just a slightly less hot period during the cooler months.
So, no....they don't use chains in the winter.
So you are saying the should only put these things in places that don't have snow? But the company trying to develop these explicitly stated they could melt off snow themselves, which is what I was commenting on.
Well, like I said. A Vermont blizzard is pretty much a showstopper for these things. Probably the same with the Dakotas, Wisconsin, Michigan, and Montana. These are also the kind of places where you'll see snow chains. Although they're illegal in certain states, due to the damage they do to the road, even when it's regular pavement. Same in Canada.
However, somewhere in the area of Tennessee, Kentucky, maybe Missouri, will get a small amount of snow, that these things should handle just fine.
Then there are all the southern states that get no snow, or at most, a few flakes during a cold spell in January, that doesn't stick around for more than a night.
And I realize it would be impossible to melt all the snow from a Vermont blizzard.
My point was, there was no mention in the article of putting these things in Japan, so what trucks do in in winter in Japan is completely irrelevant to the conversation.
I'm sure that if somebody actually thought about it, they'd figure that putting these things in North Dakota is stupid, and anywhere north of Kentucky is probably pointless.
However, there are a lot of roads in Texas, Oklahoma, Nevada, and the like, that will receive very little to zero snow, even in winter. Basically, there's at least 15 states that could completely replace their entire road system with this stuff, and generate enough electricity for the needs of themselves, and another 15 states.
Instead of snow ploughs, at most they'd need to be washed every 6 months or so. Maybe they should put water pipes in a layer under the electronics layer, so that they could all pump water through them from the Gulf of Mexico, and be self cleaning. Of course, that would also involve desalination....
And on top of that, the roof would keep a lot of snow - non-windblown stuff, anyway - off the road, and you wouldn't have to plow it as much in winter.
You do realize you're talking about a country that's over 3000 miles wide on average, right? And roughly 2000 miles north to south? And that's not including Alaska....
Add in all the little screwy subdivision roads, right up to major 4 lane highways.....I'm surprised it's only 25,000 square miles, to be honest.
According to Wikipedia, the US is roughly 3.8 million square miles in area. 25,000 square miles of roads means that roads cover only 0.66% of the surface area of the US.
Don't think that's possible, without adding an SSL layer to 802.11, which would also require that each network card or driver have a public/private key pair. And it would have to be generated automatically during install, rather than being fixed as part of the driver download.
And since we've already got secure 802.11, I doubt any researchers are going to get to work doing something like this, especially since it would, I expect, break backwards compatibility.
Having said that, Belkin makes a wireless router with dual 802.11. One key gives access to the private network, and a second allows access to only the Internet. Of course, you still have to enter a key, and non-private users would still be able to use ARP poisoning tricks and such, but it's sort of along the lines of what you want, I think.
Simply set the public encryption key as part of the SSID, and keep the private one to yourself. You'll have a safe network, and others will be able to get the key from the SSID to access the Internet with encryption.
Of course, since an attacker would also be able to get the encryption key from the SSID, it doesn't do you much good to keep things secure for your other users......
But Internet Explorer's lack of built-in support for SVG was keeping it away from mainstream use on the web.
I parsed that sentence the exact same way, intially, assuming it was a joke from the poster.
Then I realized after a few seconds that it's not Internet Explorer that was kept away from mainstream web use, but SVG that was kept away from mainstream web use _by_ Internet Explorer....
GUID, hash, whatever. It doesn't matter what you call it; if the size of the GUID/hash is smaller than the input data, there _will_ be collisions. And if it's not, then it's just a replacement for the D/L number, which doesn't solve the problem at all.
Unless it's a Smart, or an original BMC Mini, I can't think of a car that weighs 3/4 of a tonne. Pretty much everything is heavier than that. A Smart is about 725 kg, a Mini maxed out at around 686 kg, depending on the version.
The new Mini weighs 1132 kg. Probably more than the cow, unless it was one huge mother.... And most other cars go up from there in weight.
Not to say that it wouldn't make a big mess, even if the car was 75% heavier than the cow. After all, cows don't have crumple zones, so they tend to be dead weight when you hit one....
Slashdot Mirror
But that meeting, ideally, should be geeks meeting with other geeks, and hammering out interface specs.
There should not be sales, marketing, HR, upper management, or any other irrelevant staff involved. Only the project leader/manager, and the geeks in question.
If the project manager doesn't relate to the geeks (s)he's managing, then they're not the right person for the job.
And geeks can sit and talk about technology with other geeks to the wee hours of the morning.
Just ask my wife. She'll verify that.
(OMGLOLWTFBBQ!!! A /.er with a wife!!?!?!?)
Yeah... and two kids. So you can figure out what we do with our evenings.....
So trucks in America don't use chains in the winter? What do they use? If they use chains it's perfectly relevant.
A lot of places in the south of the USA don't have "winter" per se. Just a slightly less hot period during the cooler months.
So, no....they don't use chains in the winter.
So you are saying the should only put these things in places that don't have snow? But the company trying to develop these explicitly stated they could melt off snow themselves, which is what I was commenting on.
Well, like I said. A Vermont blizzard is pretty much a showstopper for these things. Probably the same with the Dakotas, Wisconsin, Michigan, and Montana. These are also the kind of places where you'll see snow chains. Although they're illegal in certain states, due to the damage they do to the road, even when it's regular pavement. Same in Canada.
However, somewhere in the area of Tennessee, Kentucky, maybe Missouri, will get a small amount of snow, that these things should handle just fine.
Then there are all the southern states that get no snow, or at most, a few flakes during a cold spell in January, that doesn't stick around for more than a night.
No...I understood your comment.
And I realize it would be impossible to melt all the snow from a Vermont blizzard.
My point was, there was no mention in the article of putting these things in Japan, so what trucks do in in winter in Japan is completely irrelevant to the conversation.
I'm sure that if somebody actually thought about it, they'd figure that putting these things in North Dakota is stupid, and anywhere north of Kentucky is probably pointless.
However, there are a lot of roads in Texas, Oklahoma, Nevada, and the like, that will receive very little to zero snow, even in winter. Basically, there's at least 15 states that could completely replace their entire road system with this stuff, and generate enough electricity for the needs of themselves, and another 15 states.
Instead of snow ploughs, at most they'd need to be washed every 6 months or so.
Maybe they should put water pipes in a layer under the electronics layer, so that they could all pump water through them from the Gulf of Mexico, and be self cleaning.
Of course, that would also involve desalination....
I dunno. Maybe they just need to call tech support....
And on top of that, the roof would keep a lot of snow - non-windblown stuff, anyway - off the road, and you wouldn't have to plow it as much in winter.
Brilliant!
I'm sure the next time it snows in Arizona, they'll all take your advice and immediately put chains on all the shipping trucks in the state. :-/
You do realize you're talking about a country that's over 3000 miles wide on average, right?
And roughly 2000 miles north to south?
And that's not including Alaska....
Add in all the little screwy subdivision roads, right up to major 4 lane highways.....I'm surprised it's only 25,000 square miles, to be honest.
According to Wikipedia, the US is roughly 3.8 million square miles in area.
25,000 square miles of roads means that roads cover only 0.66% of the surface area of the US.
That's not exactly a lot.
We would call that getting two birds stoned at once in Canada.
I don't know.....getting birds stoned sounds more like an English thing. :-)
:-/
Whoosh.
Just.....whoosh.
How you could miss that one, I have no idea.
You weren't really paying attention, were you?
Don't think that's possible, without adding an SSL layer to 802.11, which would also require that each network card or driver have a public/private key pair.
And it would have to be generated automatically during install, rather than being fixed as part of the driver download.
And since we've already got secure 802.11, I doubt any researchers are going to get to work doing something like this, especially since it would, I expect, break backwards compatibility.
Having said that, Belkin makes a wireless router with dual 802.11.
One key gives access to the private network, and a second allows access to only the Internet.
Of course, you still have to enter a key, and non-private users would still be able to use ARP poisoning tricks and such, but it's sort of along the lines of what you want, I think.
Simply set the public encryption key as part of the SSID, and keep the private one to yourself. You'll have a safe network, and others will be able to get the key from the SSID to access the Internet with encryption.
Of course, since an attacker would also be able to get the encryption key from the SSID, it doesn't do you much good to keep things secure for your other users......
And then somebody can connect to your insecure one, and use ARP poisoning to sniff all the traffic between your secure network and the Internet.
Remind me not to hire you to set up a secure network.
Your sig takes on a whole new meaning in this story......
discombobulated....
Or maybe that's one fucking badass planet. The lesson to be learned here is do not fuck with Wasp-18b.
Unless you're Chuch Norris.
Wait....
Maybe Chuck Norris is an alien from planet Wasp-18b!
Of course!
That would explain everything!!!
Well, 2012 is supposed to be a disaster!
Someone's going to be (Mg,Fe)7Si8O22(OH)2
Maybe....but not anybody on this board.
At least, not with the benefit of a second person, anyway..... :-)
Config managers don't have to be complicated or expensive (see RANCID......
We want......a SHRUBBERY!
Ni...ni...ni!!!
(For the mods....RANCID is a tool made by Shrubbery Networks....)
But Internet Explorer's lack of built-in support for SVG was keeping it away from mainstream use on the web.
I parsed that sentence the exact same way, intially, assuming it was a joke from the poster.
Then I realized after a few seconds that it's not Internet Explorer that was kept away from mainstream web use, but SVG that was kept away from mainstream web use _by_ Internet Explorer....
Just click on the yellow bar that's saying...
"DON'T click herE!1! It could KILL your compuTER!!!!1!!!!1"
That's what they usually do to install the latest WinAntivirus, so they should be able to install plugins the same way.... :-)
Regular beatings are included.
Beatings that kill you cost an extra $1000.
Well, there was one more important question that you missed:
Did you get free hamburger? :-)
GUID, hash, whatever. It doesn't matter what you call it; if the size of the GUID/hash is smaller than the input data, there _will_ be collisions. And if it's not, then it's just a replacement for the D/L number, which doesn't solve the problem at all.
Unless it's a Smart, or an original BMC Mini, I can't think of a car that weighs 3/4 of a tonne. Pretty much everything is heavier than that.
A Smart is about 725 kg, a Mini maxed out at around 686 kg, depending on the version.
The new Mini weighs 1132 kg. Probably more than the cow, unless it was one huge mother....
And most other cars go up from there in weight.
Not to say that it wouldn't make a big mess, even if the car was 75% heavier than the cow. After all, cows don't have crumple zones, so they tend to be dead weight when you hit one....
Good try. But there's one extra n in there, in uSing.
net s tart botnet
You must have had some of MS's programmers help you with the coding. That's why I'm not worried......
You missed the capitalized spaces between the command words.
Besides....how are you going to use the botnet infection to start the botnet infection?
You clearly haven't thought this through.....