Slashdot Mirror
Kids Think the Darndest Things About How Computers Work (acm.org)
"When visiting a series of eight primary school class rooms recently, CS professor Judy Robertson talked to children aged 5-12 about how computers work and discussed pictures they drew of what they thought is inside a computer," writes Slashdot reader theodp:
"In my view," Robertson writes, "computational thinking has abstracted us too far away from the heart of computation — the machine. The world would be a tedious place if we had to do all out computational thinking ourselves; that's why we invented computers in the first place. Yet, the new school curricula across the world have lost focus on hardware and how code executes on it."
She notes, "What the pictures, and subsequent classroom discussions told me is that the children know names of components within a computer, and possibly some isolated facts about them. None of the pictures showed accurately how the components work together to perform computation, although the children were ready and willing to reason about this with their classmates. Although some of the children had programmed in the visual programming language, none of them knew how the commands they wrote in Scratch would be executed in the hardware inside a computer. One boy, who had been learning about variables in Scratch the previous day wanted to know whether if he looked in his computer he would really see apps with boxes full of variables in them."
Time to get the Walk-Through Computer (1990 video) out of mothballs?
"Many of the children knew the names of the components within a computer: a chip, memory, a disc, and they were often insistent that there should be a fan in there. They knew that there would be wires inside, and that it would need a battery to make it work...."
But one student confessed that while they knew that a computer was full of both devices and code, "I am not sure what it looked like so I just scribbled."
"In my view," Robertson writes, "computational thinking has abstracted us too far away from the heart of computation — the machine. The world would be a tedious place if we had to do all out computational thinking ourselves; that's why we invented computers in the first place. Yet, the new school curricula across the world have lost focus on hardware and how code executes on it."
She notes, "What the pictures, and subsequent classroom discussions told me is that the children know names of components within a computer, and possibly some isolated facts about them. None of the pictures showed accurately how the components work together to perform computation, although the children were ready and willing to reason about this with their classmates. Although some of the children had programmed in the visual programming language, none of them knew how the commands they wrote in Scratch would be executed in the hardware inside a computer. One boy, who had been learning about variables in Scratch the previous day wanted to know whether if he looked in his computer he would really see apps with boxes full of variables in them."
Time to get the Walk-Through Computer (1990 video) out of mothballs?
"Many of the children knew the names of the components within a computer: a chip, memory, a disc, and they were often insistent that there should be a fan in there. They knew that there would be wires inside, and that it would need a battery to make it work...."
But one student confessed that while they knew that a computer was full of both devices and code, "I am not sure what it looked like so I just scribbled."
They also don‘t know how a car or a locomotive works and if they are from the South, how Evolution works.
Truth be told, most people in the tech industry don't seem to know either. Or don't want to know. Most of our infrastructure is built on layers upon layers of buggy software, as if software was a platform.
sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
Probably don't know a whole lot about how many things really work.
Primary school == ages 5-11
They're children. Teaching them intense logic and assembly would turn all but a hand full off of CS.
Same thing would happen if you went to your local bar and just asked a bunch of random adults the same question. There would be scribbling, a "i know it has a fan and cpu" and "isn't there apps inside there, i think?"
When I was in primary school, I had heard of a computer, but I did not even know what it was.
When I was in middle school, we got a C64. I knew you could play games on it, and even make your own simple games. Other than that, I did not know what it was good for and certainly did not know what was inside, or care for that matter.
Yet, somehow, by some miracle, I, as an adult, with money to buy things, am able to purchase PC components to cobble together my own machine. Even a couple hackintosh machines.
I can even, on occasion... code.
Amazingly, my lack of understand the inter-workings of a complex system in my primary school days did not hinder my life. No no.. other things were responsible for that.
This kind of thing is what American businesses thrive on -- ignorance and lack of understanding.
With this poor understanding, not just with kids, American businesses see huge potential in the crazy kind of IT services they can offer to anyone with a computer, tablet, or a phone, and the outrageous prices they can charge.
One boy, who had been learning about variables in Scratch the previous day wanted to know whether if he looked in his computer he would really see apps with boxes full of variables in them."
The children of today already assume the everyday computer and software of tomorrow with non-volatile memory, virtualization and massive parallelism.
I was going to write "Arduino, Raspberry Pi, and others like them". But then I couldn't think of any other organisations really pushing understanding of computing technology. Perhaps Micro Bit and Beaglebone?
This is where and how I started my love affair with computing. :-D That didn't stop me reading the cover-to-cover many times over :-D
Back in '84 my school library got a few Usborne books in stock - a year before we had access to a computer
https://boingboing.net/2016/02/07/usborne-releases-free-pdfs-of.html
In order to drum up support for more h-1bs in Congress, the Silicon Valley companies paid the media companies to put out stories about a "shortage of programmers". This is done in conjunction with publicly calling for increased k-12 spending on computer science education. Expanded k-12 computer science education was tried in the 70s and 80s. Most students weren't interested.
When I was 7, I thought that by writing a game's name on a floppy disk, you copy that game from one disk to another. When I was 17, I wrote a full hardware emulator. Children this young are not supposed to know the intimate details of how a machine works, give them a break.
Avantgarde Hebrew science fiction
You're right - and it's not just kids.
A couple of years ago I was asked to teach a Masters level course in software development. During one discussion, we somehow got on to the subject of cars, and what made them go. Faced with baffled faces and a stunned silence, I drilled a bit deeper and found that none of them actually knew how an internal combustion engine worked - had no idea as to what made it go other than they had to put petrol in every so often. They had cars, drove them, but none of them knew anything about the mechanism under the hood.
This reminds me of a visit to France earlier this year. My wife and I were walking past a couple when my wife slowed down, turned to me, and said "I don't think the man knows what to do about their flat tyre - the girl has just said to him that he'll have to ask someone." They were well into their 20s, but neither had a clue. With the help of my wife as a translator, I changed the wheel for them. You should have seen their faces when I 'amazed them' with my knowledge, e.g., I knew that there'd be a special adapter required to take off one of the wheel-nuts; and that it was probably in the car's glove compartment (which it was).
I'm at a loss to explain this. Where has 'curiosity' gone; especially in males!? They all seem too much into self grooming products and how they look these days.
@peetm
As a Developer for over 35 years it amazes me that most of the developers I work with have never seen the inside of any computer.
I am constantly rebuilding my computers.
The average person doesn't have to know how to build a multiplier out of transistors. They don't have to know how a CPU manages virtual register files. They don't want to know anything like that.
The average person wants to click on the icon with the child petting a fluffy dog and see the video of the child petting the fluffy dog. The average person wants the computer to magically make their lives easier and better.
Professor isn't wrong about people not grasping the fundamentals - not kids, not even 99.999% of adults - but she also doesn't understand why people use technology. She doesn't understand what they want from it. They don't want to understand it - they just want it to magically work.
Logic blocks? Digital abstractions? It's all awful transistor that barely make sense as terrible differential equations... So ugly we wrap it up with 1s and 0s to stay sane...
The horror. THE HORROR!!!
Amazing, these books were my start into computing with my primary school's Amstrad CPC 464 and later my own ZX spectrum. Really well written and pitched to explain all the fundamental concepts to children in a friendly and accessible manner. I wish we had more books at this level today.
Perhaps it is past time to remove the industry-wide dumb down http://3seas.org/EAD-RFI-respo...
get away from pre-teens. Kids are stupid. I KID you knot.
#MACMGA - but just because you are a Trump loyalist, don't shoot up a synagogue. Leave that to Trump. He'll get around to it.
Not simply grown ups, but majority of grown ups.
No, wait, not simply majority of grown ups, but majority of grown ups WORKING IN IT!
So, exactly what is news here?
Over at my YouTube channel, eg low level, bare metal hw accelerated 3D programming: https://youtu.be/fXJ11_wG_0U
As a kid I had the book 'The Way Things Work' by David Macaulay, so I knew all about the tiny mammoths inside all our technology.
These taught me more than anything else about how computers work at the hardware/machine code level.
Actually building the projects would teach me a lot more, I'm sure.
Clearly the kids who made these drawings never saw this old Sesame Street clip:
https://www.youtube.com/watch?...
Then again, if the episodes I have seen recently are any indication, I doubt Sesame Street plays the kind of really good educational clips it used to anymore (I suspect it started going downhill when someone decided they could make a lot of money selling plush toys (especially that ugly red thing) and switched the focus away from the educational clips and towards more clips featuring the Muppet characters who could be marketed via toys and such.
y'know... there's a reason why a friend of mine, when his children asked "dad, dad can we get a computer", he went up into the attic, brought down a TRS80 and a stack of byte magazines, dropped them on the table and said, "here you go!"
they looked at him like he'd grown two heads or something. when they asked him about it, he said, "when you've gone through all of the programs in there, and typed them in and seen how they run, i'll get you a PC"
i have never heard of any other parent doing this. basic self-running computers just do not exist these days. not even arduinos: they require ANOTHER COMPUTER to program them.
BBC Basic, the Jupiter ACE (which ran FORTH), the ZX-Spectrum, these were computers that were *critical* to understanding.
... then you need to get them close to the metal but make it less tedious. For instance, I would have them start with modified assembly language that was based on research, with libraries that gave kids a leg up to do cool things quickly (aka make little games, etc).
The problem with learning how computers work, it's often divorced from what kids want to use it for, aka learning for most kids will always be grunt work so you should tap into what they'd like to make the computer do and their natural curiousity and make it easier for them, kids will find a way to the goal if you setup a course specifically designed to tap into their own curioustiy and ambition - aka you have to make the grind worth the effort, otherwise kids won't be able to sustain the boring parts. You need to create a virtuous cycle of feedback that's usually difficult except for the truly gifted among us like the John carmacks of the world of Quake fame.
Fuck off Criemer.
Besides the absurdity of including 5 year olds in a survey of computer hardware knowledge, how would you explain to them the basics, in a way that doesn't result in blank stares?
Where has curiosity gone in automobile repair technicians?
My car overheated out on the highway and had to be towed in. I OK'd the repair shop of the towing company to work on it.
They assured me the water pump was fine but the electronically controlled fan was not coming on. They replaced, at considerable cost, a special ECM operating the fan. That didn't fix the car, so they recommended replacing my "plugged radiator" at considerable expense, especially in labor considering the tight "packaging" in a front-drive car.
I had the car towed a second time to a dealer repair shop. They told me the problem was the water pump. When they replaced it, this revealed that the plastic impeller of the old water pump had fractured.
I guess I am lacking in curiosity too, because the hose going to the radiator didn't warm up, which could have pointed to a plugged radiator, but the cabin heater was blowing cold, so what is the likelihood of a plugged heater core and a plugged radiator suddenly happening out-on-the-road? Catastrophic failure of the water pump -- single-point failure responsible for both symptoms?
I learned something, but this cost me a pricey double repair bill on a 23-year-old car to which I have a sentimental attachment.
Besides the absurdity of including 5 year olds in a survey of computer hardware knowledge, how would you explain to them the basics, in a way that doesn't result in blank stares?
It's a good exercise both in communication skills (shifting your point of view) and creating a top-down view of a complex body of knowledge. Often those heavily involved with a field can't abstract.
This post contains no rudeness or derision of any kind. All arguments are friendly. Terms and exclusions may apply.
Then Linus and crew is out of a job then.
Shai Schticks:"You don't make peace with friends, you make peace with enemies"
I don't know, but their knowlege looks just fine to me. That one drawing emphasises two fans - I presume you can hear and/or see them easyest - and just has simple connections between components, not even plus and minus, but let's be honest: Do *you* know how the north and southbridge play together? Or which faulty resistor makes your memory defunct and which one the USB? The last plan of a computer I saw was the C64 layout that came with the manual - and that was pretty much abstracted away too, containing only information that some tinkerer would need.
That someone thinks a piece of cheese is inside a computer is obviously someone who won't be an engineer but probably a manager or a farmer or something. But children think like that - no big deal.
Example: As a 4 year old kid I watched the Stan & Laurel piece where they take a rife and shoot at a house and at the same time it explodes because of some dynamite or something. That was the joke but as a 4 year old I didn't get it, couldn't connect the dots between one shot showing a burning fuse, them shooting and the house exploding. I went for a few years thinking that rifles have the power to blow up houses with one shot. Big deal. Children reason as good as they can, and if they learn the details behind things they correct their opinions. That's how reasoning works.
Bottom line: Open up a computer and show them the insides. They'll learn pretty quickly all the stuff software people like us know. Maybe even more.
We suffer more in our imagination than in reality. - Seneca
Asked to use imagination for filling in blanks, they use imagination for filling in blanks rather than run away screaming like a responsible adult.
Most of the stuff they come up with still sounds saner than what creationists imagine.
> whether if he looked in his computer he would really see apps with boxes full of variables in them.
Yes and yes - if you had good-enough (X-Ray) eyes.
Amazingly similar to 'back of the napkin' sketches from our enterprise system architects..
Talk to kids about how anything else works internally and you'll get equally comical responses. The inner workings of a computer are complicated. Even the far simpler abstract model that most developers have in their minds is not kid friendly at all. They'll learn soon enough, or not, because most of them really don't need that kind of insight.
Look, you can tell me all you want that 5 year olds don't know how cars work and such, but this also includes older ages.
The problem is not that they can't tell you how huge, complex machines work together, the problem is the alarming lack of knowledge on how things work generally.
Education systems in the west especially are horribly lacking in showing how the machines work around us at a younger age.
Most of it is being pushed in to the secondary education stages, 10-12 and up depending on where you live.
Some of it isn't even there! Some of it is tertiary education, locked behind stupidly high college / university fees in some instances. (even in "free" countries)
Where the fuck did practical, hands-on experience go to?
The younger you are, the more fluid your brain is.
Younger people are literally smarter by default, it is how we learn.
Leaving that to the older years gives is a horribly basic view of the world and creates societal retards.
I'm not ancient, not even old, I'm only 32 (feel 82!), but even in my school days, we had a lot of good, solid hands-on experience with models and abstractions of complex devices like computers, TVs, cars, etc.
Playing with little electronics breadboards with components all split up and you could experiment, like the classic 7-segment display timer.
Our education works better with hands-on experiences than trying to create an abstract model of how something works.
SEEING and FEELING it creates a more concrete memory. Even more so if it is fun. (which theory work generally isn't!)
Theory should back up interaction in the earlier years. There are some topics you simply cannot do practical visual, tangible abstractions for, but most can be.
Any kids who spwns much time around me end up knowing how an engine works, because I show them any chance I get.
Showing them the internal workings of a CPU is a bit more difficult. My four-year-old will have some understanding within the next few years, somehow. She already understands wireless internet uses radio waves from the towers she sees, or our home router / AP. She understands that her iPad can't do video in the car because we're too far from the router and the radio waves can't reach. She can't SEE the radio waves, though, and that limits understanding.
Someone mentioned twenty-somethings who can't change a tire. My four-year-old changes the tires on her Lightening McQueen toy, using a little plastic lug wrench. I've made sure she's paying attention whenever I help someone change a tire.
Less the apt but unnecessary dig at creationists.
It's progress when people don't have to know what's inside the box. People used to have to know how their car worked so that they could work on it all the time. Cars used to have daily maintenance which had to be performed by a mechanic. Now they go thousands of miles before the first time an inspection even has to be performed. Computers, the same. No more checking for corrosion on wire-wrap terminals.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Most people aren't programmers and never will be.
ZIP
"Any sufficiently advanced technology is indistinguishable from magic." -- Arthur Clarke
Try explaining to someone that a transistor works by using a pump to move imaginary holes through magic sand so that teeny tiny lightning bolts can go from one end to the other.
I would like to think that I had a very good CS and EE college program. I understand the theory of what a transistor does, and how they are made. I understand how transistors are arranged into memory, logic, and math units (yes, I have had to make logic gates / JK flip flops / adders, etc. out of transistors). I know how these pieces come together into a simple CPU. I know how to program at the bit level, the assembly level, the low-level C languages all the way up to PHP, Python, and JavaScript. I have written simple compilers and very simple OSes in various classes. I know lots about the theory of how hard drives work, how solid state drives work, how LEDs and LCDs work. I have *decades* of experience in fixing and repairing PCs and other electronics.... and all the head-knowledge about "WHY" things work is pretty much irrelevant to day-to-day life and work - and this is to me with a very strong technical background - and everyone else just wants the f(n) thing to WORK.
In "20000 leagues under the sea", Captain Nemo boasts of a library of 12,000 volumes - more than many royals of the day. And while 12000 was a high number at one point - it is pretty small by today's standards. If you were to document how to build a CDROM and a player, for example - you would have to know how find, pump, and refine oil, use oil to make plastics, understand how to make lasers, all the magic sand bits that go into making a microprocessor, how to refine metals into a stepper motor, etc. You could probably spend 12000 volumes JUST on the technology that is encompassed into a CD reader ,,, and these are so worthless as to be disposable. I have thrown away perfectly good CD readers because the customer wants a DVD+/-RW drive. Drive bad? Throw it away and put in a new one because it is far, far, cheaper than trying to diagnose and fix it.
The world would be a tedious place if we had to do all out computational thinking ourselves; that's why we invented computers in the first place.
No, we invented computers not to avoid the computational thinking, but to speed up computational repeat work, in particular the work of code breaking.
Using computers to avoid thinking is a new use case.
It's not so long ago that you had to be able to think and troubleshoot far more than the average person in order to use computers.
From the article:
The children, like most Windows users, wanted to know why their computers "freeze", speculating that it could be because the chip is asleep or that too many people are using Wi-Fi.
Suck it MS, and your shitty Windows product, too!
First, they're discussing it with children. Surprise, they don't know things.
Second, we've gone most of history with most of the population not understanding the technicalities of the most complex technology at the time. Technology is only continuing to get more complex and more specialized requiring even more time to learn. The majority of people will just never understand and will use it like a black box. It's not a tragic loss since this is how it's always been. You only think something changed because computers used to be the realm exclusively of nerds. Now that they have widespread usage among the mainstream this is just a return to the norm like every other complex piece of machinery.
Do you think those same children have any idea how a car works? A train? A plane? An elevator? The plumbing is their house? GPS?
This is why we shouldn't be trying to teach everyone to code. We'll wind up with the homeopathy of programming.
One difference is that end users' expectations of software functionality have increased.
Internationalization How many languages can geoWrite display within one document? Can it display, for example, all the characters of a newspaper in Chinese, as well as right-to-left cursive text in Arabic or top-to-bottom text in Mongolian? In how many languages can its user interface be presented? Accessibility How easily can users who are blind or hard of sight navigate GEOS? Can it read a document out loud to the user while describing all controls? Pixel density and depth The Commodore 64 computer's display has only 320x200 pixels, and the selection of colors that may appear in a single 8x8-pixel area is strictly limited. This limits the usefulness of geoPaint or geoDraw for editing detailed photographs or illustrations with fidelity comparable to print. Common platform Back in the day, software had to be written in assembly language. In order to ship the same application for computers using 6502, 6809, Z80, 68000, and 8086 family CPUs, the program had to be rewritten by hand, and all bug fixes in one version had to be propagated to other versions by hand. Though the versions for one CPU family could share their "model" code, such as Commodore 64, Atari 800, and Apple II, or Macintosh, Atari ST, and Amiga, or ZX Spectrum and MSX, there was no efficient way for ports to different ISAs to share any code. In addition, versions for different computer platforms took up multiples of space on store shelves. A developer could produce highly optimized software for one platform, but then the application would have to be so compelling that users of one brand of computer would be willing to buy a second computer just to run one application. Nowadays, all major web application players (commonly called "browsers") have decent support for JavaScript and the HTML DOM.What I learned is that I should have stood up to my wife and executed on my plan to drive her 24-year-old Chrysler without working A/C up to my dad's place and exchange it for our 21-year-old Camry with powerful A/C so we weren't under pressure to repair the 23-year-old Ford to drive around the in-laws coming into town on a hot, summer holiday weekend. My wife admitted later that my plan could have saved us a bunch of money, either with a do-it-yourself water pump replacement or making a family decision without pressure on whether to junk the car.
What I learned is that I should have just paid the towing mileage to our house because the mileage charge on a long tow is small compared to even a minor repair charge, and the car could be started and moved into the garage without an operating cooling system. What I learned is that the online Ford Forum suggested that based on the symptoms, I had a water pump problem and that changing a water pump is doable on that car for a home mechanic.
Your suggestion that the dealer is the highest-cost option is well known, but the non-dealer tow operator has more than 10 people in its operation and is not any cheaper. They didn't appear to know what they were doing whereas the dealer did. We don't have a local car mechanic because I either do the work myself or take the car to a tire shop run by a friend-of-the-family up by Dad's place -- where I was headed.
As to the "blobs" inside the car, we are talking about a conventional liquid cooling system that has been on cars for decades, the only fancy thing being a relay box to switch the electric fan on, a part that costs about a hundred bucks from the auto parts store, only a repair place, all repair places I know about, will charge three times as much. The same goes for the water pump. As to why the huge markup on replacement parts, it probably has to do with the overhead employing more than 10 people, and much of that overhead is probably healthcare. Even a "lean" high co-pay health plan is pricy. So it is modern medicine that makes fixing cars and every other service so expensive.
As to junking a car that breaks down after 5 years, a replacement for the Ford runs about 25K these days. Yes, you cannot "touch" anything on a car these days without running up 700 or 800 dollars in charges. If I have such a charge every other year, I am still "ahead" of the straight-line depreciation on a 25K car, even if it is 23 years old. It is just that I got hit with two such charges because the tow-place repair shop didn't know that if both the radiator hose and the cabin heat is cold, the fan is not coming on because the temperature sensor isn't "seeing" anything and the water pump is probably busted. Also, the mileage charge on the tow is not that much, so if you break down within, say, 30 miles of home, just tow the fine thing home rather than expect the tow-operator's shop to fix it.
As to "kids these days, they can name the computer parts, but they cannot tell you how it operates", heck, there are repair shops with techs who don't know the (mechanical) basics of how a car operates.
Although some of the children had programmed in the visual programming language, none of them knew how the commands they wrote in Scratch would be executed in the hardware inside a computer.
Okay, you software developers out there, how many of you understand every step of how your code gets converted to binary, then executed on the silicon, down how to make logic gates from transistors and how those transistors actually work?
(Not that we need to, but I imagine some number of the nerdiest among us actually do.)
-- Alastair
Yet, the new school curricula across the world have lost focus on hardware and how code executes on it.
Please, describe the time and place where focusing on hardware and how code (I'm assuming assembly) executes on it, was taught in grade school?
Given what's described, it sounds like the kids know more than what they need to know. Given how few people actually ever deal with how hardware executes code, versus more people who are going to need to code (in probably abstract and managed languages), this sounds like going in the right direction.
Most adults don't understand how tech works.
The are *users* of technology and considered (sometimes) technically literate but most cellphone, tablet and PC users have no idea what goes on inside their device or how it communicates with the world.
Circa 1978, my University had Burroughs 6700. On the first week of classes we had a tour of the building that housed it. I recall asking my guide which one of these boxes is the Operating System.
My father called electricity, "juice." When I was young, I through the pole transformers were where the juice was stored.
That everything will magically be ok when they turn 18, but until then they just need to keep their head down, do their homework and their chores, and not ask too many questions.
My parents sent me to all kinds of summer camps and various things, but they left me with large gaps in my knowledge about motors, motorized vehicles, and power tools until well into my early 20s. Really it was only getting into automotive tech while in lower division college that lead to me understanding how a lot of this stuff worked.
Computers on the other hand I've known most of the details about since I was a 10 year old, but I was an outlier in that regard, having started at 3 and both gotten books on the subject and explanations of the insides of chips (including both prints of the cpu transistor layouts and expanations of how an ALU worked) Although the nuances of them again took good professors in college to completely understand. I'm sure if I had been allowed to explore more as a child my knowledge in those areas would have been higher, but I kept being told it was too complicated/unsafe for a child and I could learn it when I grew up.
Those never had a "focus on hardware and how code executes on it".
So far that has been material for college/university level education.
All the different Spectre security holes is proof of this.
A lot of people know how some parts work but nobody knows how everything works.
But we don't need to know all that either. Depending on what you want to do, different abstractions and simplifications are good enough. Kind of knowing how a computer works is good enough for most programmers, and for others it's enough to know that the "f" on your mobile phone brings up Facebook.
One of the things we covered in my LISP course was how to create a LISP compiler for a system, when the compiler code itself is written in LISP. The trick is to write a compiler which can interpret some basic LISP functions. Then use that to compile the other more complex LISP functions needed by the compiler (written in LISP). Then use that to compile a complete LISP compiler. Nobody really knows what's going on in the machine code for the compiler, since the code giving you the full functionality of LISP was made by a compiler which was made by a compiler.which in turn was made by a compiler which was made by hand-coding.
When I was a kid, I had fully open systems with circuit diagrams. The idea of "DRM" didn't even really exist.
Today, most kids don't even have superuser access to their phone.
That's fucked up, and we're going to be in trouble in another generation.
A government is a body of people notably ungoverned - AC
How the electoral college worked.
Damn, not knowing the essentials or basics is really endemic.
Kids are dumb as hell, who cares what they think?
That 1990 video hurt me, and something inside died a little.
99% of programmers would answer the same way so what is the point ?
This is very serious stuff I'm not surprised people who are not interested in computers don't know how they work.
I mean we've been living in our bodies for hunder of thousands of years but most of us can't tell you how they work.
So there's nothing wrong here, it's been a long while since humans have understood things that are too complicated for one person to understand on her own from scratch. Thats why we have universities and such.
you start thinking about it and make up the oddest conjectures. As long as you can not or are unable to test those conjectures, it seems logical. And you start convincing other people of your logic, because you think you are correct.
Religion works the same way.
There's several Star Trek and science fiction films which outline this problem. It's possibly unavoidable as we as humans want to live mostly on the surface of an ever expanding sphere, not in the middle or bottom.