From the two videos I saw, it didn't look like the pilot lost control. It looks more like he attempted an inverted loop, but misjudged the amount of altitude he needed to complete it. Then again, I wasn't there.
The part about the Partriot missile isn't at all clear on explaining how the computational error resulted in the mistake. A quick search led to this article, which is far more plausable: http://www.mc.edu/campus/users/travis/syllabi/381/patriot.htm
It's programmers who suck at math, not computers. Computers do exactly what you tell them to, which includes how they're designed to interpret what you tell them to do. This was a tragic example of what can happen when reusing legacy software.
Like it or not, it has to be done. Why? Because your competitors do it and your customers expect it. Nobody says you have to like it. I have yet to personally encounter people or a situation where it prevented me from getting shit done and getting it done right.
That's absolutely right. Some considered assasinating the Emperor, which only would've made every last man, woman and child fight to the death under any and all circumstances. Hell, it took two of these bombs to convince the powers that be to cease. The Emperor got on the radio (hardly anyone ever heard him speak before) and told the Japanese people that it would not be in their best to continue the War. In fact, many of them thought they won the War! The claims that they were just about to surrender are completely and entirely false.
I'm concerned that at some point I won't be able to get a cell phone without a camera. I can't even bring a cell phone to work that has a camera nor a voice recorder in it due to security restrictions (proprietary and classified). I really don't want a phone to dictate which carrier I use, either. I switched carriers last year and couldn't bring my phone with me because it was TDMA and I needed CDMA. As long as it is reliable and can store numbers, I'm happy.
I repeated myself, because the OP felt I wasn't clear. If you actually read the thread first, you'd see that. And I didn't equate betrayal of a person with being a traitor to their country. I said he's a traitor to his fellow veterans. Please read closely, folks. I'm tired of having to clarify what should otherwise be clear.
I'm not disputing that there were American soldiers who committed war crimes. It's the fact that he felt he could speak for everyone instead of just himself. If anything I said is incoherent, it's because I'm telling you what you don't want to hear.
He [Kerry] is a traitor to those former American POWs who endured years torture by their foreign captors in attempt to force them [the former POWs] to admit that they [the former POWs] committed war crimes even if they [the former POWs] did not.
Re:This is something I've always wanted to know
on
The Hidden Swing State?
·
· Score: 1, Interesting
For starters, he's a traitor to those POWs who endured years of torture to get them to say they committed war crimes even if they didn't.
I've been using Panix for over 10 years. They have $10/month shell-only bring-your-own access accounts. CGI, IMAP, et. al. included. I highly recommend them. Highly competent personnel. Well administered. Worth every penny.
Don't core dump on your resume. A resume is a teaser. Its purpose is to capture interest. Keep it to one page as much as possible. A prospective employer doesn't want to sit there reading your life story when they have a stack of other resumes to go through. Save the details for the interview and, perhaps, a summary of qualifications, which you should have handy when you go to the interview. Targeted resumes are very important. One thing that makes me cringe is seeing people write out these long lists of operating systems, programming langauges, applications, office suites, and the like. Lists like those are meaningless. Instead, under your job experience list, give a short description of what you did and include the relevant OSs/langs/apps/suites. But again, keep it brief and maintain scope. Drop the generic mission statements. A good interviewer will guage how well-rounded you are, so leave those lists off the resume, too. Briefness, specifics, and relevance are what you should concentrate on. Forget the fancy fonts. Keep the layout neat and readable. It's a resume, not a royal proclamation. This has worked very well for me. And remember, be sure you can back up and immediately recollect anything you write on your resume. Think of it this way. Your resume is like the front page of a newspaper, the headlines, the stuff that makes you buy the paper. Interviews and everything else are the rest of the newspaper, the juicy details.
I'm still using my old IBM PS/1 I got when I was in high school as my NAT. It just works, period. 8 MB of ram (started with 4) and no harddrive running FloppyFW. I think there was even a 16 Mhz version besides my 20, but I'm not sure.
Did you ever stop to think that it's ultimately not up to the developers? The game companies are, first and foremost, businesses. Considering what happened to Loki, porting mainstream games to Linux is not profitable (yet, anyway). Too bad, too. I bought Loki's ports of SOF and Q3A and thoroughly enjoyed playing them.
Where I work (not the gaming industry), developers' ideas are constantly getting shot down due to lack of money. And it often doesn't matter how good the idea is or whether it will make things "better" or not.
Slashdot Mirror
You're right. I stand corrected. Thanks!
Maybe the first FOSS one.
From the two videos I saw, it didn't look like the pilot lost control. It looks more like he attempted an inverted loop, but misjudged the amount of altitude he needed to complete it. Then again, I wasn't there.
The part about the Partriot missile isn't at all clear on explaining how the computational error resulted in the mistake. A quick search led to this article, which is far more plausable: http://www.mc.edu/campus/users/travis/syllabi/381/patriot.htm
It's programmers who suck at math, not computers. Computers do exactly what you tell them to, which includes how they're designed to interpret what you tell them to do. This was a tragic example of what can happen when reusing legacy software.
then my Asswhistles.
Like it or not, it has to be done. Why? Because your competitors do it and your customers expect it. Nobody says you have to like it. I have yet to personally encounter people or a situation where it prevented me from getting shit done and getting it done right.
...when there's a hit and run accident? Unless witnesses can remember a bar code, it's going to make tracking criminals down that much more difficult.
That's absolutely right. Some considered assasinating the Emperor, which only would've made every last man, woman and child fight to the death under any and all circumstances. Hell, it took two of these bombs to convince the powers that be to cease. The Emperor got on the radio (hardly anyone ever heard him speak before) and told the Japanese people that it would not be in their best to continue the War. In fact, many of them thought they won the War! The claims that they were just about to surrender are completely and entirely false.
Um, no. It's a voice transmitter and receiver.
I'm concerned that at some point I won't be able to get a cell phone without a camera. I can't even bring a cell phone to work that has a camera nor a voice recorder in it due to security restrictions (proprietary and classified). I really don't want a phone to dictate which carrier I use, either. I switched carriers last year and couldn't bring my phone with me because it was TDMA and I needed CDMA. As long as it is reliable and can store numbers, I'm happy.
Linux is a kernel, not an OS.
I repeated myself, because the OP felt I wasn't clear. If you actually read the thread first, you'd see that. And I didn't equate betrayal of a person with being a traitor to their country. I said he's a traitor to his fellow veterans. Please read closely, folks. I'm tired of having to clarify what should otherwise be clear.
I'm not disputing that there were American soldiers who committed war crimes. It's the fact that he felt he could speak for everyone instead of just himself. If anything I said is incoherent, it's because I'm telling you what you don't want to hear.
He [Kerry] is a traitor to those former American POWs who endured years torture by their foreign captors in attempt to force them [the former POWs] to admit that they [the former POWs] committed war crimes even if they [the former POWs] did not.
For starters, he's a traitor to those POWs who endured years of torture to get them to say they committed war crimes even if they didn't.
She probably still is.
...Catherine Mary Stewart.
I've been using Panix for over 10 years. They have $10/month shell-only bring-your-own access accounts. CGI, IMAP, et. al. included. I highly recommend them. Highly competent personnel. Well administered. Worth every penny.
Don't core dump on your resume. A resume is a teaser. Its purpose is to capture interest. Keep it to one page as much as possible. A prospective employer doesn't want to sit there reading your life story when they have a stack of other resumes to go through. Save the details for the interview and, perhaps, a summary of qualifications, which you should have handy when you go to the interview. Targeted resumes are very important. One thing that makes me cringe is seeing people write out these long lists of operating systems, programming langauges, applications, office suites, and the like. Lists like those are meaningless. Instead, under your job experience list, give a short description of what you did and include the relevant OSs/langs/apps/suites. But again, keep it brief and maintain scope. Drop the generic mission statements. A good interviewer will guage how well-rounded you are, so leave those lists off the resume, too. Briefness, specifics, and relevance are what you should concentrate on. Forget the fancy fonts. Keep the layout neat and readable. It's a resume, not a royal proclamation. This has worked very well for me. And remember, be sure you can back up and immediately recollect anything you write on your resume. Think of it this way. Your resume is like the front page of a newspaper, the headlines, the stuff that makes you buy the paper. Interviews and everything else are the rest of the newspaper, the juicy details.
I'm still using my old IBM PS/1 I got when I was in high school as my NAT. It just works, period. 8 MB of ram (started with 4) and no harddrive running FloppyFW. I think there was even a 16 Mhz version besides my 20, but I'm not sure.
More like a bane.
...have been around for almost 30 years.
...is an antique.
Lazy? How can you make such a stupid comment?
Did you ever stop to think that it's ultimately not up to the developers? The game companies are, first and foremost, businesses. Considering what happened to Loki, porting mainstream games to Linux is not profitable (yet, anyway). Too bad, too. I bought Loki's ports of SOF and Q3A and thoroughly enjoyed playing them.
Where I work (not the gaming industry), developers' ideas are constantly getting shot down due to lack of money. And it often doesn't matter how good the idea is or whether it will make things "better" or not.
Birth Control