Introducing /run

If your design you system with newbies as the priority, you will only have newbies on your system. Have you ever heard of Windows guru? If you have, it likely does not mean: "someone who is powerful with windows and can do lots with it", but rather "someone who knows and understands all the dirty hacks and ways around or to avoid them". Does anybody aspire to that?

I for one am reminded with many reasons any time I touch a windows (rare) PC, why I don't like it. Long untraversable (and weirdly hidden and tangled) paths which seem different on every windows version are one of the reasons. GUIs seem of no help to me to understand the layout either since each GUI twists and pretends the paths start at different roots.

So, you may believe that newbies understand long names better, but I suspect that what really happens is that nobody understands them. So, if the only way you can make a newbie as smart as an expert is by making the expert dumb, perhaps you have not really gained anything?

But again, read the previous posts. It is not about old gurus or being harder to type. It is about being able more easily read things, to visualize and remember a whole directory structure in one's head fairly easily. It's about making problems smaller and more easy to comprehend, more local. Your PC is not the WWW, it should not need long global directory names to separate itself from the rest of the PCs on the internet.

Keep the simple things simple. Yes, "simple", not "dumbed down". Assume (and enable) some level of competence and you will be rewarded with it. Assume idiots (and prevent progress) and you will get...