3 ms·
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
by walrus01 8y ago
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.
"where is your data?"
"uhhh, it's in the app, or in the cloud"
"yes, but specifically where?"
"i dunno"
The comment here nails it: https://news.ycombinator.com/item?id=18350671 https://news.ycombinator.com/item?id=18350671
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.
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 did install Windows.
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.
- ryandrake 8y ago> "where is your data?" > "uhhh, it's in the app, or in the cloud" > "yes, but specifically where?" > "i dunno" We can keep going: “It’s in /home/walrus01/docs” “But specifically where? What physical drive?” “It’s on /dev/sda2” “What cylinder/track/sector?” At some point it stops mattering practically. The abstractions presented to users today are often such that it doesn’t matter if the user knows what path something is stored in.
- brokenmachine 8y agoIt will matter when that data goes missing or the abstraction stops working for whatever reason. From what I've seen, people who don't understand or aren't interested to learn about computers will only learn precisely one method to achieve exactly what they are trying to do. Not knowing how it works is a very fragile way of doing things and could fall over at any minute, and that's bound to be the worst possible minute, and in the worst possible way.