The increasing use of walled garden things like iOS which abstract the file system away from the end user, making it impossible to know what the system's actual directory structure looks like, certainly doesn't help.<p>"where is your data?"<p>"uhhh, it's in the app, or in the cloud"<p>"yes, but specifically where?"<p>"i dunno"<p>The comment here nails it: <a href="https://news.ycombinator.com/item?id=18350671" rel="nofollow">https://news.ycombinator.com/item?id=18350671</a><p>Children and teenagers these days spend a lot of time using passive media consumption devices. An iPad is great if you're watching youtube or netflix passively, not so great at all if you want to create your own content, edit it, manipulate it, back it up, transfer it places, etc. Touchscreen devices and phones are great for browsing web pages. It's a media portal with a walled garden app store, not a real computer, though its hardware may be capable of more than its operating system allows it to do.<p>This comment could easily devolve into a "get off my lawn" rant, but I seriously believe that people who learned how to use x86 type computers from a command line first are much more capable of understanding what's going on underneath a GUI. If you spent time mucking about with config.sys and autoexec.bat settings in MS-DOS 3.3 and 5.0, a long time before you saw a Windows GUI, you could immediately grok what was going on when you <i>did</i> install Windows.<p>I am not a big fan of Arch Linux, but in the modern era there's a lot of value to getting people to learn what is going on when they do a brand new Arch install on an empty disk. What's happening with fdisk, partitioning, formatting, grub2/bootloader, etc. And why it's happening. If you don't want to go that far in an educational environment, start people from a debian stretch barebones install with CLI only + sshd.