Kids, computers and Dr. Seuss
"Have you ever wondered what might have happened if Dr Seuss wrote technical manuals for computers............
If a packet hits a pocket on a socket on a port,
And the bus is interrupted as a very last resort
and the address of the memory makes your hard disk read abort
Then the socket packet pocket has an error to report!
If your cursor finds a menu item followed by a dash,
And the double-clicking icons put our window in the trash,
And your data is corrupted 'cause the index doesn't hash,
then your situation is hopeless and your systems gonna crash!
If the label on your cable on the gable at your house,
says the network is connected to the button on your mouse,
But your packet wants to tunnel to another protocol,
That's repeatedly rejected by the printer down the hall.!
And your screen is all distorted by the side effects of gauss,
So your icons in the window are as wavy as a souse.
Then you may as well reboot and go out with a bang.
Cause as sure as I'm a poet , the suckers gonna hang!
When the copy of your CD's getting scratchy on the disk,
and the micocode instructions cause unnecessary RISC,
then you have to flash your memory and you'll want to RAM your ROM.
Quickly turn off your computer and be sure to tell your Mom!"
(with slight tweaks by yours truly to somewhat modernize)
To be on topic...while bustapr is correct, many parents are intimidated by those options and what they should do to better control the environment of their kid's computer. So if a company wants to provide an arguably preconfigured parent friendly computer, its hard for me to consider that a bad thing.
Of course...the flip side of the argument is that if the parent needs help making a PC safe for their kid...that parent is pretty much screwed once the kid gets savy enough to circumvent the protection that the parent doesn't really understand to begin with. Then it becomes a weird mix of challenging respect and understanding with the all consuming powers of curiosity.
Facebook
Twitter
Instagram