Thank you for all the responses! It confirmed some of the thoughts i had and help me set an idea of what needed to be done.
More info on the orgnization and LAN party can be found here:
http://personal.bgsu.edu/~randlem/xngc/
WASTE is a wonderful technology, but as a practical alternative to a P2P program like KaZaA it is not. After it first came out there was a test done to see how many simultaneous clients could survive on the network and still have it work as anticipated. Due to the mesh topology of the network it was only able to support about 120 simultaneous users before it became very unstable. I'm sure with some optimizations you could get that over 200, but I highly doubt you'll ever come close to the 2 million plus connected to KaZaA at any given time.
I realize that it's important to some people to have their native language represented in what they type and in their communication but isn't this more trouble then it's worth? As it stands now, the system works well. Sure you may not be able to get a umlaut in your domain, but is that really a just cause to change the entire fscking DNS system?
Odd how your.sig can say "The true measure of a good coder is not how complex his code is, but how simple" yet you yourself cannot see the true simplicity of a well executed C program over the cludge of a well executed C++ program.
I'll give you that OOP is the best solution to certain problems, but nothing will ever compare with the shear power and cleanliness of procedural code.
Back in the early day of WASTE, after it's relase and subsequent pull, i helped test the network load of 100+ nodes. Nobody really knew what would happen at that load.
Turns out that the mesh it creates suckes when it gets scaled over 100 nodes. You could hack the protocol to provide for a central mediation server (and keyserver), but that would detract from the fluidity of the mesh.
WASTE is a exellent tool for people who need to share files and chat in an strongly encrypted enviroment, like a dev house, but for a widespread P2P app, it would need some serious development work.
He's decided on the all the main aspects and is currently building the final prototype. After that's complete in the next few weeks, everything hardware will be frozen.
I've been a member of the sites boards for a while now, and I've seen all the work he's put into it. It will be a finished product.
/me points at Debian 3.0 Testing running on P1 Laptop.
Makes a great, inexpensive mobile hacking station. It's only got a 1GB hdd and no CDROM so i had to be very selective about what OS to use. Debian at the time was the only one that had a floppy based install and was compact. Had i know about it at the time i would have figured out some way to get Vector installed on it. Seems to be a more complete, less "oh, crap i need to download a package".
Speaking as a current CS student at a "major" university in the Midwest, I can honestly say that there is a HUGE lack of good programming practices taught. From the beginning you are taught to write code that is potentially buggy at best. I believe that it stems from the fact that a majority of people who are entering CS programs had little interaction with coding before their studies begin. It takes nearly 3 semesters of studies before the student is capable of writing correct, basic C++ code.
By that time in their 4 year program they should be preparing to start, if they choose, their Junior co-op. They are for the most part still un-baptisied in the ways of algorithims and data structures and more advanced topics such as networks and operating systems. Within the next 4-5 semesters there is little time for them to learn how to write secure code, because of all the other nessary skills they need to learn before graduation so they are even marketable. It has been my experience that writing secure code is pushed aside, in the pursuit of getting the students in-and-out with the basic skills they need to get a low-level job.
In some ways this is a copout because the case could be made that a student shouldn't have to learn what a business doesn't use in order to be marketable. However it should be the coders job to catch the security breaches, because after all it is their code. If the coder doen't know to watch out for a buffer overflow or other potential security breaches, because they never learned about it in their standard studies, then it becomes a problem.
But that's just my take on it...
It's not a sense of superiority but rather a sense of intolerance for the simplicity of the example. I would hope that most people who have grown up using the English system of measures would have a good grasp on the weight of a ton. A good visual example is nessary but as i interpreted the article is seemed as if the writer was trying to hard to illustrate the shear weight of the clouds buy substuting elephants in for actually physical measurements.
By the way what makes you think that a person has any better grasp on the magnitude of the weight of an elephant compared to the maginitude of the weight of a ton?
It isn't saying much when you have to relate the measurement of weight to an elephant so the populous that reads it can grasp the magnitude of the number. In fact I find that rather pathetic...
1. Trucks use diesel fuel, not gas.
2. Trucks use less fuel then you think. Before the late 80's and early 90's the adverage trucker would get between 2-3 mpg with weight on, and now it's up to 6-10mpg. Plus you have tho think about how large a truck engine is. My fathers Cat engine displaces 13 liters. My car's engine only displaces 3.8 liters and it's on the large side of "modern" cars.
3. A tipical truck is driven over 500 mi a day. Therefore it would make more sense to want a tax on the fuel the company buys, and not on the milage the truck drives. You can reduce fuel consumption, but you can't reduce the distance a truck travels.
Slashdot Mirror
With a purposeful grimace and a terrible sound
He pulls the spitting high tension wires down
Helpless people on a subway train
Scream bug-eyed as he looks in on them
He picks up a bus and he throws it back down
As he wades through the buildings toward the center of town
Oh no, they say he's got to go go go Godzilla
Oh no, there goes Tokyo go go Godzilla
History shows again and again
How nature points up the folly of men
Looks like it's time to fire up the flamethrowers...
Interm Website
Thank you for all the responses! It confirmed some of the thoughts i had and help me set an idea of what needed to be done. More info on the orgnization and LAN party can be found here: http://personal.bgsu.edu/~randlem/xngc/
My P1 75MHz laptop does everything i need it to do...including run a wireless card...
Read the subject.
WASTE is a wonderful technology, but as a practical alternative to a P2P program like KaZaA it is not. After it first came out there was a test done to see how many simultaneous clients could survive on the network and still have it work as anticipated. Due to the mesh topology of the network it was only able to support about 120 simultaneous users before it became very unstable. I'm sure with some optimizations you could get that over 200, but I highly doubt you'll ever come close to the 2 million plus connected to KaZaA at any given time.
I realize that it's important to some people to have their native language represented in what they type and in their communication but isn't this more trouble then it's worth? As it stands now, the system works well. Sure you may not be able to get a umlaut in your domain, but is that really a just cause to change the entire fscking DNS system?
Odd how your .sig can say "The true measure of a good coder is not how complex his code is, but how simple" yet you yourself cannot see the true simplicity of a well executed C program over the cludge of a well executed C++ program.
I'll give you that OOP is the best solution to certain problems, but nothing will ever compare with the shear power and cleanliness of procedural code.
Back in the early day of WASTE, after it's relase and subsequent pull, i helped test the network load of 100+ nodes. Nobody really knew what would happen at that load. Turns out that the mesh it creates suckes when it gets scaled over 100 nodes. You could hack the protocol to provide for a central mediation server (and keyserver), but that would detract from the fluidity of the mesh. WASTE is a exellent tool for people who need to share files and chat in an strongly encrypted enviroment, like a dev house, but for a widespread P2P app, it would need some serious development work.
He's decided on the all the main aspects and is currently building the final prototype. After that's complete in the next few weeks, everything hardware will be frozen. I've been a member of the sites boards for a while now, and I've seen all the work he's put into it. It will be a finished product.
/me points at Debian 3.0 Testing running on P1 Laptop. Makes a great, inexpensive mobile hacking station. It's only got a 1GB hdd and no CDROM so i had to be very selective about what OS to use. Debian at the time was the only one that had a floppy based install and was compact. Had i know about it at the time i would have figured out some way to get Vector installed on it. Seems to be a more complete, less "oh, crap i need to download a package".
I thank God everyday i live in the United States
Speaking as a current CS student at a "major" university in the Midwest, I can honestly say that there is a HUGE lack of good programming practices taught. From the beginning you are taught to write code that is potentially buggy at best. I believe that it stems from the fact that a majority of people who are entering CS programs had little interaction with coding before their studies begin. It takes nearly 3 semesters of studies before the student is capable of writing correct, basic C++ code. By that time in their 4 year program they should be preparing to start, if they choose, their Junior co-op. They are for the most part still un-baptisied in the ways of algorithims and data structures and more advanced topics such as networks and operating systems. Within the next 4-5 semesters there is little time for them to learn how to write secure code, because of all the other nessary skills they need to learn before graduation so they are even marketable. It has been my experience that writing secure code is pushed aside, in the pursuit of getting the students in-and-out with the basic skills they need to get a low-level job. In some ways this is a copout because the case could be made that a student shouldn't have to learn what a business doesn't use in order to be marketable. However it should be the coders job to catch the security breaches, because after all it is their code. If the coder doen't know to watch out for a buffer overflow or other potential security breaches, because they never learned about it in their standard studies, then it becomes a problem. But that's just my take on it...
It's not a sense of superiority but rather a sense of intolerance for the simplicity of the example. I would hope that most people who have grown up using the English system of measures would have a good grasp on the weight of a ton. A good visual example is nessary but as i interpreted the article is seemed as if the writer was trying to hard to illustrate the shear weight of the clouds buy substuting elephants in for actually physical measurements. By the way what makes you think that a person has any better grasp on the magnitude of the weight of an elephant compared to the maginitude of the weight of a ton?
It isn't saying much when you have to relate the measurement of weight to an elephant so the populous that reads it can grasp the magnitude of the number. In fact I find that rather pathetic...
Bowling Green OH still got power...suck that Toledo.
1. Trucks use diesel fuel, not gas.
2. Trucks use less fuel then you think. Before the late 80's and early 90's the adverage trucker would get between 2-3 mpg with weight on, and now it's up to 6-10mpg. Plus you have tho think about how large a truck engine is. My fathers Cat engine displaces 13 liters. My car's engine only displaces 3.8 liters and it's on the large side of "modern" cars.
3. A tipical truck is driven over 500 mi a day. Therefore it would make more sense to want a tax on the fuel the company buys, and not on the milage the truck drives. You can reduce fuel consumption, but you can't reduce the distance a truck travels.