That's like when NASA put in a request for a convertable GTO (sports car) to pull heavy lifting body designs (shuttle is a lifting body) and film them for research. Of course it was denied. They then put in a request for something like a "aerodynamic research tow vehicle with film platform" and it was approved. And thusly, the lifting body concept was proven and established.
The biggest bottleneck right now is the availibity of high-grade silicon.
Don't you see! It's obvious! Oil companies drill through what? SAND! Where does silicon come from? That's right! SAND! It's all a conspiracy by the oil companies!
Come to think of it...what is on the moon? SAND! That's proof that the oil companies are behind the faked moon landings too!
total failure of a previous project to scale using C++ and OO techniques.
But history shows that the reason most C++ projects fail is not because of the language, but because of low performance programmers that insist on using OO-idioms without regard for C++-implications.
I can't tell you how many times I've seen projects fail because of poor design, no design, poor requirements, poor programmers, bad managers, and horrible schedules, but ultimately blame the language because no one wants to accept where the finger really points.
Which do you think is more likely; managers and programmers step up to higher ups and say the project failed because we're idiots or, they step up and say, the language failed us?
Simple fact is, C++ is a hard language which often requires additional time in schedules. Sadly, schedules are usually one of the first things people attempt to compress and normally those schedules are based on years of experience with languages like C. The end result is bad programmers write bad code which is then not optimized and poorly debugged, to meet a bad schedule which is later compressed by bad management, which failed to properly estimate in the beginning.
a web server that scales better on a single CPU than Apache
I really wish people would stop using Apache as a performance metric. Apache's priority has always been scalability, security, and features, but not performance. The fact that it's historically faster than MS' effort is an embassessment for MS, but it does not mean it's the holy grail of web servers.
Simple fact is, it's common to find web servers which are much, much faster than Apache. Some web servers which are faster than apache are even written in languages like python.
ook up data base fields seems SO routine and not at all patent-worthy.
In other words, Amazon is use a browser feature that was specifically supported to remember information between sessions. The mechanism is intentionally broad. The simple fact that cookies existed for Amazon to leverage is prior art.
This is like building a race track and distributing the plans for cars that will race on it. All cars that have historically raced on it are white. Now someone comes along and patents a blue race car on this specific trace track, while including details of shifting gears and pressing the gas pedal.
In other words, they patented the process and tools which already existed specifically to allow what amazon is patenting. Not only is it obvious but the fact that they can implement the patent proves prior art.
I have to run but I wanted to post just real quick. NAT is common for many providers, especially so in Asia.
Switching IPv6 should require less computing power than NAT. At worst, it should be on par. Having said that, where NAT is in place, it must do both NAT and routing. If you remove NAT, you are by definition performing less work. Thusly, simply routing IPv4 or IPv6 requires less overhead (and lower latency) than IPv[46] + NAT.
As IPv6 becomes the norm, hardware support will become common place too.
The original point still stands...there is nothing inherently high latency in IPv6, which is what the original message to which I replied implied..
Actually, I had a 64-bit OpenOffice installed. It was primarily third party games (NWN, America's Army, Teamspeak, etc) which required the 32-bit environment. At the time, 64-bit Blender was also experimental with known stability issues.
I thought hellfires were laser-guided. Don't they have to wait until the opponents are vapor above a crater before they go home?
I think you are thinking of the old TOWs, which are wire guided. The Hellfire missile is a fire and forget missile. Once it's launched, it independently seeks its target.
One of the cool things an Apache Longbow does is settle into the treeline. They stop descending when the tops of the trees have been clipped by the main rotors. This allows them to remain hidden while they scan for targets. They then pick their targets (radar is above the rotor), pop up, fire, and go home. Some seconds later their targets are smoking.
Also, during Operation Anaconda in Afganistan, many Apaches returned home with many, many holes in their main rotors from small arms fire. The rotors can take a serious beating and still hold together. In fact, during that same operation, one Apache took a direct RPG hit in its transmission. It flew home despite the total lose of fluid. Another Apache took a direct RPG hit on its FLIR and it too returned home.
Despite how rugged it is, just don't turn on the rotor heat! The apache is suppose to be an all weather craft but the rotor heat is not suppose to be used because the blades will delaminate.:)
I can tell you that this is not true. Rotor imbalance is a serious problem for any helicopter. My brother is an instructor in Apache Longbows, so he knows.
(project abandoned once it was complete, your tax dollars at work.)
For what it's worth, my brother bunked with a pilot on that project. I had a chance to briefly talk with him about it. He agreed it wasn't what was promised but he could not go into details on it with me. At any rate, what most people don't realize is that the research from the project will resurface into another project down the road, so it's not totally wasted. The good news is, they didn't put it into production...that would have been a complete waste of tax dollars.
In fact, as I understand it, a new revision of the Longbow is now planned. I believe part of the avionics research from the Commanche project will directly feed back into the next revision of the Longbow.
You would be amazed at the number of Vietnam era aircraft which are still flying. I have flown on a CH-47 Chinook and noted odd textured/patches on most of the helicopters on the flight line. When I got off the helicopter, I asked my friend, who is a mechanic that works on them, why they were all patched. He laugh and said most of the helicopters saw action during Vietnam and that those were bullet holes which had been patched.
The problem with running 64-bit Linux is you wind up with what almost equates to two Linux installations. This is because you wind up having both a 64-bit and 32-bit environment, otherwise you can't run 32-bit software. Worse, lots of software that you may want to play with has never been ported to 64-bit. This means you either wind up compiling these odds and ends as 32-bit or you wind up porting it to 64-bit. Again, this means a 32-bit and 64-bit development environment, plus all those dang libraries.
I got tired of constantly porting software to compile as 64-bit. Worse, there exists a number of audio issues. If for example, you want to use a 32-bit application, which plays audio, on your 64-bit system, which happens to use the old OSS interface, you'll be required to have the full 32-bit audio support tools in place and you'll still have problems muxing your audio. I no longer remember the exact details but I can tell you that Teamspeak was at the top of my curse list.
Worse, I also had a lot of application stability problems with my 64-bit applications which seemed to hint that many of the 64-bit applications were not quite ready for the 64-bit world. Granted, this was a year or two ago (wow...I guess it has been that long) and things have probably, greatly improved...but I'm certainly not in a hurry to go back to a 64-bit Linux desktop. Maybe next year...
That's only an issue today. The post implied that IPv6 was inherently a high latency proposal. It isn't, nor should it be. Once IPv6 becomes available to the masses, latency should be on par with current IPv4 deploymnets. In fact, latency may actually go down as routing can be more effecient, potentially requiring fewer hops if NAT is currently anywhere in your IPv4 routes.
Isn't that because it's tunneling IPv6 over IPv4? So of course the latency is going to be much higher. I would be hard pressed to imagine why latency would be higher for IPv4 versus IPv6 so long as it's an apples to apples comparison. If what I read is correct on the URL you provided, it's like comparing IPv4 verses IPv4 traveling over an VPN. So of course the latency is going to be higher...but one has nothing to do with the other if a fair comparison is your intention.
Please correct me if I failed to properly interpret "tunneling", as stated on that site.
Makes we wonder how much business they lost from people legally downloading music. I'm not sure why it must surely be illegal downloads that lost them their antiquited business.
Wonder if buggy whip businesses blamed their failure on everything other than a change in technology base and a simple change in the times.
I wonder if the RIAA has any clue that they are currently posed to become the buggy whip buisness of this millenium.
But the local governments *do* have the option of simply not enforcing them.
Well, for what it's worth, that was also one of the stipulations given by the Feds. They made it clear that the slower speeds not only had to be restored but they had to be enforced. Besides, it only takes a couple of cities that need the revenue to screw up "look'n the other way."
Well, here is something to keep in mind about cops. Sure, most of them are serious assholes, but they got that way from being with serious assholes every-friggen-day. Think about it. They are trained to expect the worst in people so they can stay alive. How do you think you would change if everyday, 50 people lied to face? How about if most everyone you had contact with just commited a crime? So on and so on. These guys deserve your pity. I know I sure wouldn't want to be a cop. Being a cop means willingly accepting the dark side.
State officials don't want to change them because they fund the police force via speeding tickets.
Not so. Maybe a decade ago several states tried to raise their speed limits. The Federal government came back and said lower your speed limits or you lose federal highway dollars. The states complied. In other words, many states are more than happy to raise the legal speed limit but Washington has made it clear that the states have no say if they want to continue to receive federal highway dollars.
I hate to be pedantic, but a range of around 430 miles seems much more realistic for a 172 on 42 gallons. I don't have a 172 POH here but if you really pull the throttle back to get extra range, chances are it will be faster and cheaper to simply drive unless you have a heck of a tail wind.
Feel free to cross check what I'm saying at this website.
I have seen a video of a Moller Skycar during a tethered flight. What a joke. It never left ground effect and its stability was a smoldering pile waiting to happen. I'm sure that is why you don't see it and that is why it is not generally available.
In fact, his project has all the earmarks of the flying saucer efforts (Avro Aircar) efforts during the 50s. The only improvement Moller has over Avro's efforts is it uses less fuel and the risk of falling into the propulsion system is greatly reduced. Aside from that, neither has left ground effect.
He wants the plane to fly itself. (He also requires what amounts to a complete revamp of the ATC system, but NASA and others are already researching something similar to his needs in that arena)
Then don't hold your breath. Funding for the next found of ATC/FAA restrucuring is going before Congress this year. Based on the currently announced plans, it will take 10-20 years before all planes adopt the new ADS-B technology (Info here or here. That means several decades before Moller's car can hope to fly its self. And if he requires something other than GPS and ADS-B, then his car won't be off the ground for two plus decades, easily.
Am I the only one that sees the oxymoron here... "the world's first commercial spaceport" vs "Governor Bill Richardson recently secured 33 million dollars from the state legislature for the final design, and a proposed 0.25% sales tax increase in Dona Ana County,
Makes as much sense as county and state funded football fields. At least this can hope to further the interests of all men.
While I agree with your grumblings, I also believe it is the job of a government to prop up critical infrastructure. Items such as telephone, roads, railways, and even plane travel deserve some loving...if needed. Believe it or not, even commercial aviation is frequently used for military purposes (transport) because they can do it cheaper and faster than the military can. So which would you rather pay, the goverment to do it slowly and cost 20x more than it should or for the government to pay for a commercial entity to do it cheaper and faster?
One way or another, you're going to be paying for it.
Slashdot Mirror
There is no "distributed" in crashing these desktop apps.
;)
What if I'm running remote desktop while I do it? Aha!
That's like when NASA put in a request for a convertable GTO (sports car) to pull heavy lifting body designs (shuttle is a lifting body) and film them for research. Of course it was denied. They then put in a request for something like a "aerodynamic research tow vehicle with film platform" and it was approved. And thusly, the lifting body concept was proven and established.
The biggest bottleneck right now is the availibity of high-grade silicon.
Don't you see! It's obvious! Oil companies drill through what? SAND! Where does silicon come from? That's right! SAND! It's all a conspiracy by the oil companies!
Come to think of it...what is on the moon? SAND! That's proof that the oil companies are behind the faked moon landings too!
total failure of a previous project to scale using C++ and OO techniques.
But history shows that the reason most C++ projects fail is not because of the language, but because of low performance programmers that insist on using OO-idioms without regard for C++-implications.
I can't tell you how many times I've seen projects fail because of poor design, no design, poor requirements, poor programmers, bad managers, and horrible schedules, but ultimately blame the language because no one wants to accept where the finger really points.
Which do you think is more likely; managers and programmers step up to higher ups and say the project failed because we're idiots or, they step up and say, the language failed us?
Simple fact is, C++ is a hard language which often requires additional time in schedules. Sadly, schedules are usually one of the first things people attempt to compress and normally those schedules are based on years of experience with languages like C. The end result is bad programmers write bad code which is then not optimized and poorly debugged, to meet a bad schedule which is later compressed by bad management, which failed to properly estimate in the beginning.
a web server that scales better on a single CPU than Apache
I really wish people would stop using Apache as a performance metric. Apache's priority has always been scalability, security, and features, but not performance. The fact that it's historically faster than MS' effort is an embassessment for MS, but it does not mean it's the holy grail of web servers.
Simple fact is, it's common to find web servers which are much, much faster than Apache. Some web servers which are faster than apache are even written in languages like python.
ook up data base fields seems SO routine and not at all patent-worthy.
In other words, Amazon is use a browser feature that was specifically supported to remember information between sessions. The mechanism is intentionally broad. The simple fact that cookies existed for Amazon to leverage is prior art.
This is like building a race track and distributing the plans for cars that will race on it. All cars that have historically raced on it are white. Now someone comes along and patents a blue race car on this specific trace track, while including details of shifting gears and pressing the gas pedal.
In other words, they patented the process and tools which already existed specifically to allow what amazon is patenting. Not only is it obvious but the fact that they can implement the patent proves prior art.
I have to run but I wanted to post just real quick. NAT is common for many providers, especially so in Asia.
Switching IPv6 should require less computing power than NAT. At worst, it should be on par. Having said that, where NAT is in place, it must do both NAT and routing. If you remove NAT, you are by definition performing less work. Thusly, simply routing IPv4 or IPv6 requires less overhead (and lower latency) than IPv[46] + NAT.
As IPv6 becomes the norm, hardware support will become common place too.
The original point still stands...there is nothing inherently high latency in IPv6, which is what the original message to which I replied implied..
Actually, I had a 64-bit OpenOffice installed. It was primarily third party games (NWN, America's Army, Teamspeak, etc) which required the 32-bit environment. At the time, 64-bit Blender was also experimental with known stability issues.
I thought hellfires were laser-guided. Don't they have to wait until the opponents are vapor above a crater before they go home?
I think you are thinking of the old TOWs, which are wire guided. The Hellfire missile is a fire and forget missile. Once it's launched, it independently seeks its target.
One of the cool things an Apache Longbow does is settle into the treeline. They stop descending when the tops of the trees have been clipped by the main rotors. This allows them to remain hidden while they scan for targets. They then pick their targets (radar is above the rotor), pop up, fire, and go home. Some seconds later their targets are smoking.
:)
Also, during Operation Anaconda in Afganistan, many Apaches returned home with many, many holes in their main rotors from small arms fire. The rotors can take a serious beating and still hold together. In fact, during that same operation, one Apache took a direct RPG hit in its transmission. It flew home despite the total lose of fluid. Another Apache took a direct RPG hit on its FLIR and it too returned home.
Despite how rugged it is, just don't turn on the rotor heat! The apache is suppose to be an all weather craft but the rotor heat is not suppose to be used because the blades will delaminate.
I can tell you that this is not true. Rotor imbalance is a serious problem for any helicopter. My brother is an instructor in Apache Longbows, so he knows.
(project abandoned once it was complete, your tax dollars at work.)
For what it's worth, my brother bunked with a pilot on that project. I had a chance to briefly talk with him about it. He agreed it wasn't what was promised but he could not go into details on it with me. At any rate, what most people don't realize is that the research from the project will resurface into another project down the road, so it's not totally wasted. The good news is, they didn't put it into production...that would have been a complete waste of tax dollars.
In fact, as I understand it, a new revision of the Longbow is now planned. I believe part of the avionics research from the Commanche project will directly feed back into the next revision of the Longbow.
You would be amazed at the number of Vietnam era aircraft which are still flying. I have flown on a CH-47 Chinook and noted odd textured/patches on most of the helicopters on the flight line. When I got off the helicopter, I asked my friend, who is a mechanic that works on them, why they were all patched. He laugh and said most of the helicopters saw action during Vietnam and that those were bullet holes which had been patched.
The problem with running 64-bit Linux is you wind up with what almost equates to two Linux installations. This is because you wind up having both a 64-bit and 32-bit environment, otherwise you can't run 32-bit software. Worse, lots of software that you may want to play with has never been ported to 64-bit. This means you either wind up compiling these odds and ends as 32-bit or you wind up porting it to 64-bit. Again, this means a 32-bit and 64-bit development environment, plus all those dang libraries.
I got tired of constantly porting software to compile as 64-bit. Worse, there exists a number of audio issues. If for example, you want to use a 32-bit application, which plays audio, on your 64-bit system, which happens to use the old OSS interface, you'll be required to have the full 32-bit audio support tools in place and you'll still have problems muxing your audio. I no longer remember the exact details but I can tell you that Teamspeak was at the top of my curse list.
Worse, I also had a lot of application stability problems with my 64-bit applications which seemed to hint that many of the 64-bit applications were not quite ready for the 64-bit world. Granted, this was a year or two ago (wow...I guess it has been that long) and things have probably, greatly improved...but I'm certainly not in a hurry to go back to a 64-bit Linux desktop. Maybe next year...
That's only an issue today. The post implied that IPv6 was inherently a high latency proposal. It isn't, nor should it be. Once IPv6 becomes available to the masses, latency should be on par with current IPv4 deploymnets. In fact, latency may actually go down as routing can be more effecient, potentially requiring fewer hops if NAT is currently anywhere in your IPv4 routes.
For us, IPv6 has been a checkbox but next year, it starts to be deployed.
This is starting to change. More and more government projects are starting to mandate IPv6 support.
Isn't that because it's tunneling IPv6 over IPv4? So of course the latency is going to be much higher. I would be hard pressed to imagine why latency would be higher for IPv4 versus IPv6 so long as it's an apples to apples comparison. If what I read is correct on the URL you provided, it's like comparing IPv4 verses IPv4 traveling over an VPN. So of course the latency is going to be higher...but one has nothing to do with the other if a fair comparison is your intention.
Please correct me if I failed to properly interpret "tunneling", as stated on that site.
Makes we wonder how much business they lost from people legally downloading music. I'm not sure why it must surely be illegal downloads that lost them their antiquited business.
Wonder if buggy whip businesses blamed their failure on everything other than a change in technology base and a simple change in the times.
I wonder if the RIAA has any clue that they are currently posed to become the buggy whip buisness of this millenium.
But the local governments *do* have the option of simply not enforcing them.
Well, for what it's worth, that was also one of the stipulations given by the Feds. They made it clear that the slower speeds not only had to be restored but they had to be enforced. Besides, it only takes a couple of cities that need the revenue to screw up "look'n the other way."
Well, here is something to keep in mind about cops. Sure, most of them are serious assholes, but they got that way from being with serious assholes every-friggen-day. Think about it. They are trained to expect the worst in people so they can stay alive. How do you think you would change if everyday, 50 people lied to face? How about if most everyone you had contact with just commited a crime? So on and so on. These guys deserve your pity. I know I sure wouldn't want to be a cop. Being a cop means willingly accepting the dark side.
State officials don't want to change them because they fund the police force via speeding tickets.
Not so. Maybe a decade ago several states tried to raise their speed limits. The Federal government came back and said lower your speed limits or you lose federal highway dollars. The states complied. In other words, many states are more than happy to raise the legal speed limit but Washington has made it clear that the states have no say if they want to continue to receive federal highway dollars.
I hate to be pedantic, but a range of around 430 miles seems much more realistic for a 172 on 42 gallons. I don't have a 172 POH here but if you really pull the throttle back to get extra range, chances are it will be faster and cheaper to simply drive unless you have a heck of a tail wind.
Feel free to cross check what I'm saying at this website.
I have seen a video of a Moller Skycar during a tethered flight. What a joke. It never left ground effect and its stability was a smoldering pile waiting to happen. I'm sure that is why you don't see it and that is why it is not generally available.
In fact, his project has all the earmarks of the flying saucer efforts (Avro Aircar) efforts during the 50s. The only improvement Moller has over Avro's efforts is it uses less fuel and the risk of falling into the propulsion system is greatly reduced. Aside from that, neither has left ground effect.
He wants the plane to fly itself. (He also requires what amounts to a complete revamp of the ATC system, but NASA and others are already researching something similar to his needs in that arena)
Then don't hold your breath. Funding for the next found of ATC/FAA restrucuring is going before Congress this year. Based on the currently announced plans, it will take 10-20 years before all planes adopt the new ADS-B technology (Info here or here. That means several decades before Moller's car can hope to fly its self. And if he requires something other than GPS and ADS-B, then his car won't be off the ground for two plus decades, easily.
Am I the only one that sees the oxymoron here... "the world's first commercial spaceport" vs "Governor Bill Richardson recently secured 33 million dollars from the state legislature for the final design, and a proposed 0.25% sales tax increase in Dona Ana County,
Makes as much sense as county and state funded football fields. At least this can hope to further the interests of all men.
While I agree with your grumblings, I also believe it is the job of a government to prop up critical infrastructure. Items such as telephone, roads, railways, and even plane travel deserve some loving...if needed. Believe it or not, even commercial aviation is frequently used for military purposes (transport) because they can do it cheaper and faster than the military can. So which would you rather pay, the goverment to do it slowly and cost 20x more than it should or for the government to pay for a commercial entity to do it cheaper and faster?
One way or another, you're going to be paying for it.