Anyway, with the question. First thing a child should know is how to get around on the computer. This includes command prompts and everything. Once they are truely mastered at this, I'd find some free compilers and teach a little bit of basic.
As long as you're starting with the command prompt, give them a BASIC interpreter that works in text only. Let them start by entering commands and seeing the results right then. Next, show them how to enter and run a program and let them experiment. The important thing with children is instant results. Their attention span isn't as long, yet, as an adults, so you have to give them lots of feedback. Once they have an idea of what happens when they do things, bring them into a GUI language, such as VB; it's similar to what they know, and gives them a chance to experiment in a GUI, with graphics. Once they get their feet wet, and are really interested (if they are) you can worry about more advanced languages. The important thing at the beginning is getting and keeping their interest, and the less hurdles you put between their entering something and seeing what happens, the more likely you are to do that.
But in most cases, you only see the movie once. Games you see over and over for days, weeks or months on end. The effect is stronger, and lasts longer. That's not to say the movie ratings system may not need tweeking, but it does explain why the games people are sricter.
(The US military is infamous for being trigger happy, and I'm sure that the USCG will do us proud in that regard.)
Part of the Coast Guard's job is stopping smugglers. Any ship coming in without the transponder is a possible smuggler, and they're going to get stopped. If they don't stop, the Coast Guard is allowed to open fire if needed. That's just doing their job. If you don't like it, try getting their rules of engagement changed. You won't succeed, but have fun trying if you feel that strongly about it.
Back when I was in Uncle Sam's Navy, it was commonly said that you had to be at least six feet tall to join the Coast Guard; that way, if your ship sank, you could wade ashore. Later, after I left the Navy, I told a Coastie officer about it; he'd never heard it before and found it quite funny. I'm glad to see they're going farther out now, and need more tracking devices to do their job. I hope it's funded properly and implemented. Jokes aside, their work is important, hard and sometimes dangerous. Let's give them what they need to things even better.
I gather you didn't bother to read the quote before pasting it in. It starts off with, "To legally enter a U.S. port..." That means that once this is in place, ships without those transmitters won't be allowed to enter U.S. ports. I presume that any ship without the transmitter in working order will be turned away.
As far as volcanos go, you don't need to be on the edge of a plate for one to form, just near a thin spot. (Not that you have any in SD, mind you.) Earthquakes don't happen only at the edges of the great big plates, but along cracks between smallish ones as well. Also, quakes can make themselves felt for long distances if they're big enough. The New Madrid Quake was felt in Philidelphia and rang church bells in Boston. Imagine what it must have been like within a hundred miles or so of the epicenter! (To give you an even better idea how big that one was, the ground dropped so far that the Mississippi was running backwards for three days filling it up!)
Most of the compatability issues were taken care of in the BIOS, which needed to be customized to the machine. You also needed to get the screen codes right, but most programs had setup programs to help you with this. Sometimes you needed to edit an assembly overlay, assemble it, bring everything into memory in the right order and save it as a new program, and that was always a royal PITA. In case you haven't guessed, I'm not talking about things I learned from history books, but from my memories of using CP/M.
If Ken had been on the show in an earlier year he would have left after his 5 day run and few people would know who he is.
I agree. I happen to know the first undefeated 5-day champion from when the show first came back on the air. Nobody's heard of her, nobody remembers her but she doesn't care. She just gets on with her life and doesn't worry about it. She's also glad she never came up against Ken, because he's so fast and so sharp.
Knowing the answer and pressing the buzzer isn't always enough. A friend of mine was on recently and lost a question because she asked, "What is a glass harmonium," instead of, "What is a glass harmonica?" She told me later that she knew the answer at the time, but the wrong word just came out.
What else do you expect? NASA is wedded to running the Shuttle, because that keeps 20,000 people on its payroll, whether it flies or not. The Shuttle Fleet is badly outmoded, needs replacing, but as long as NASA is in charge, it's not going to happen.
A good answer, in general, but it misses my point. I was trying to explain why every agency tries to expand its own mandate. Sometimes it does make sense to add something to an existing agency, sometimes to create a new one. But no matter what, each agency will try to expand no matter how much better things would be seperating the responsibilities into two or more different sets of people.
No, the Apple wasn't the first "mainstream PC," because back in the 70's CP/M was mainstream. One of the reasons it was so popular is that it wasn't tied to one set of hardware manufactured by one company. It could be adapted to any 8080 or Z80 machine with any terminal because the terminal codes weren't hard-coded into the systm. There was also a multi-user version, MP/M, so that multiple users could share to some extent the same 8" floppies.
...the Apple computer, which can be justifiably named the first personal computer...
Er...uh...I don't think so. CP/M was there years before the Apple, and there was a big (for the time) user base of CP/M computers. Not just in business, but hobbyists as well.
I don't know, of course, what would happen if my "representative" were of my party. In my old district, others of my party had the same results, and friends in the other party agreed that it appeared that party membership was the deciding factor as a general rule. Here, I've only sent a message to my new congresscritter once, and gotten no answer.
You haven't shown proof that anyone has actually gone from toiling in a factory on minimum wage to suddenly producing "intellectual property" so we'll assume nobody actually have and you just made it up
Lack of proof is not proof that something doesn't exist. How about somebody working for minimum wage in a factory to keep food on the table while he writes a novel? I'm sure that's happened many times even though I can't point to a specific example.
Since when is it ruining someone else's livelihood? So if Toyata someday comes out with a car that's as good as a Mercedes and sells it for less, are the Japanese destroying the Germans?
But that's not what's happened. A better analogy would be if Toyota stole the plans for the Mercedes, started making them and sold theirs for less than the original. What you suggested was simply compitition.
What you dont realize is that 'elected officals' only listen to people that are worthy of their time. ( i.e. people or corporations that can 'donate' huge amounts to their campaigns... )
Or, in my case, are registered in their party. I lived for eighteen years in a district controlled by the opposite party and asked for help several times. Not once did I even get a reply. Now, I've moved to a different district, controlled by the same party and am getting the same lack of response. I'm not naming which party, because it doesn't matter. I'm sure there are congrisscritters in my party that are just as partisan in their day-to-day dealings with their "constituants."
Sure, man pages exist, but even once you learn that man does what help really should the man pages are generally written by programmers for programmers.
That's what info is for. Trust info; info is your friend!
For many people "free" suggests poor quality as in "you get what you pay for".
A very important point. Often, in getting something new accepted, it's important to ask yourself how your potential customers will interpret your explanation of why they should change. If the people controlling the purse strings think "free software" means low quality and lack of support, they won't go for it. Calling it "open source" avoids that, even if they don't understand the advantages of having access to the source.
Slashdot Mirror
Write a trojan that infects it, and name it Sherman.
As long as you're starting with the command prompt, give them a BASIC interpreter that works in text only. Let them start by entering commands and seeing the results right then. Next, show them how to enter and run a program and let them experiment. The important thing with children is instant results. Their attention span isn't as long, yet, as an adults, so you have to give them lots of feedback. Once they have an idea of what happens when they do things, bring them into a GUI language, such as VB; it's similar to what they know, and gives them a chance to experiment in a GUI, with graphics. Once they get their feet wet, and are really interested (if they are) you can worry about more advanced languages. The important thing at the beginning is getting and keeping their interest, and the less hurdles you put between their entering something and seeing what happens, the more likely you are to do that.
But in most cases, you only see the movie once. Games you see over and over for days, weeks or months on end. The effect is stronger, and lasts longer. That's not to say the movie ratings system may not need tweeking, but it does explain why the games people are sricter.
Part of the Coast Guard's job is stopping smugglers. Any ship coming in without the transponder is a possible smuggler, and they're going to get stopped. If they don't stop, the Coast Guard is allowed to open fire if needed. That's just doing their job. If you don't like it, try getting their rules of engagement changed. You won't succeed, but have fun trying if you feel that strongly about it.
Back when I was in Uncle Sam's Navy, it was commonly said that you had to be at least six feet tall to join the Coast Guard; that way, if your ship sank, you could wade ashore. Later, after I left the Navy, I told a Coastie officer about it; he'd never heard it before and found it quite funny. I'm glad to see they're going farther out now, and need more tracking devices to do their job. I hope it's funded properly and implemented. Jokes aside, their work is important, hard and sometimes dangerous. Let's give them what they need to things even better.
I gather you didn't bother to read the quote before pasting it in. It starts off with, "To legally enter a U.S. port..." That means that once this is in place, ships without those transmitters won't be allowed to enter U.S. ports. I presume that any ship without the transmitter in working order will be turned away.
As far as volcanos go, you don't need to be on the edge of a plate for one to form, just near a thin spot. (Not that you have any in SD, mind you.) Earthquakes don't happen only at the edges of the great big plates, but along cracks between smallish ones as well. Also, quakes can make themselves felt for long distances if they're big enough. The New Madrid Quake was felt in Philidelphia and rang church bells in Boston. Imagine what it must have been like within a hundred miles or so of the epicenter! (To give you an even better idea how big that one was, the ground dropped so far that the Mississippi was running backwards for three days filling it up!)
Really? You mean that when the USAF uses strong lasars for targetting, they're pinpointing their own positions? I don't think so.
In Real Life, a lasar beam can't be seen unless there's some sort of dust or fog in the air for it to reflect from.
Most of the compatability issues were taken care of in the BIOS, which needed to be customized to the machine. You also needed to get the screen codes right, but most programs had setup programs to help you with this. Sometimes you needed to edit an assembly overlay, assemble it, bring everything into memory in the right order and save it as a new program, and that was always a royal PITA. In case you haven't guessed, I'm not talking about things I learned from history books, but from my memories of using CP/M.
I agree. I happen to know the first undefeated 5-day champion from when the show first came back on the air. Nobody's heard of her, nobody remembers her but she doesn't care. She just gets on with her life and doesn't worry about it. She's also glad she never came up against Ken, because he's so fast and so sharp.
Ah, but there is a Dollywood. Of course it's in Tennessee, not California.
Knowing the answer and pressing the buzzer isn't always enough. A friend of mine was on recently and lost a question because she asked, "What is a glass harmonium," instead of, "What is a glass harmonica?" She told me later that she knew the answer at the time, but the wrong word just came out.
What else do you expect? NASA is wedded to running the Shuttle, because that keeps 20,000 people on its payroll, whether it flies or not. The Shuttle Fleet is badly outmoded, needs replacing, but as long as NASA is in charge, it's not going to happen.
Do you pay in dollars, rubles or galleons?
A good answer, in general, but it misses my point. I was trying to explain why every agency tries to expand its own mandate. Sometimes it does make sense to add something to an existing agency, sometimes to create a new one. But no matter what, each agency will try to expand no matter how much better things would be seperating the responsibilities into two or more different sets of people.
It's simple. The more things they regulate, the more power they have, the more people they need and the bigger their budgets get.
No, the Apple wasn't the first "mainstream PC," because back in the 70's CP/M was mainstream. One of the reasons it was so popular is that it wasn't tied to one set of hardware manufactured by one company. It could be adapted to any 8080 or Z80 machine with any terminal because the terminal codes weren't hard-coded into the systm. There was also a multi-user version, MP/M, so that multiple users could share to some extent the same 8" floppies.
Er...uh...I don't think so. CP/M was there years before the Apple, and there was a big (for the time) user base of CP/M computers. Not just in business, but hobbyists as well.
I don't know, of course, what would happen if my "representative" were of my party. In my old district, others of my party had the same results, and friends in the other party agreed that it appeared that party membership was the deciding factor as a general rule. Here, I've only sent a message to my new congresscritter once, and gotten no answer.
Lack of proof is not proof that something doesn't exist. How about somebody working for minimum wage in a factory to keep food on the table while he writes a novel? I'm sure that's happened many times even though I can't point to a specific example.
But that's not what's happened. A better analogy would be if Toyota stole the plans for the Mercedes, started making them and sold theirs for less than the original. What you suggested was simply compitition.
Or, in my case, are registered in their party. I lived for eighteen years in a district controlled by the opposite party and asked for help several times. Not once did I even get a reply. Now, I've moved to a different district, controlled by the same party and am getting the same lack of response. I'm not naming which party, because it doesn't matter. I'm sure there are congrisscritters in my party that are just as partisan in their day-to-day dealings with their "constituants."
That's what info is for. Trust info; info is your friend!
A very important point. Often, in getting something new accepted, it's important to ask yourself how your potential customers will interpret your explanation of why they should change. If the people controlling the purse strings think "free software" means low quality and lack of support, they won't go for it. Calling it "open source" avoids that, even if they don't understand the advantages of having access to the source.