Secondly, when we're talking about learning, using a command line will probably (definitely?) stimulate reasoning and abstract thinking, whereas you can emulate the effect of a touch screen with a door bell.
Addendum: Of course, you can emulate a keyboard with an iPad, but then what's the point? You even lose the tactile feedback a keyboard gives you.
I'd go out on a limb and claim that a kid will be better off by using actual water colors instead of a water color app on the iPad. In the same vein I think kids might have more important things to do at the age of three than typing commands into XMonad (not that it hurts if it's not the only thing they do).
In fact there are numerous studies that show the importance of practical and physical experiences for the development of abstract thinking, math etc. during early childhood.
I am not sure that many kids 2-5 get that much out of the command line. They are still working on building their visual skills, exploring tangibles etc.
I am all for command lines if the kid get it, just think it's rare that they get that much out of it in that young age.
A CLI on the other hand is a very good abstract reasoning thing - it's on the same level as teaching a kid to read, or counting. And like reading I think it's a very valuable exercise whether the kid "gets" it or not.
The iPad on the other hand allows for emulating the reality the kids know and thus allow them to play around and learn abstraction based on where they are mentally.
This is I believe pretty well established.
And how does one become familiar with computers if they only live in that world? This is no different than any other professional bringing their kids to the shop/office to learn what daddy does.
I learned to operate the VCR before I learned to operate a computer. One thing does not exclude the other.
We are talking about kids here not computer scientists. If they have it in them they will have no problem switching.
> daddy is a woodworker, so here's some stone tools
Are you suggesting that if "daddy is a developer" that he's only using a touch screen for development? Or that development of touch screen apps is all a developer does? I'm confused by this statement.Edit: Maybe I'm just not reading this right. Did you mean:
daddy is a woodworker, so here's some stone[-working] tools
or daddy is a woodworker, so here's some stone tools [used for
woodworking]Now he just needs to teach them emacs.
You can open and close programs, change their layout, move between and resize them. All with, what, 7 shortcuts?
With mouse-based WM's there's click to focus, click and drag, right click, lots of buttons and icons everywhere and you have to constantly work to make the relevant information visible.
There's a reason why people don't go back after using tiling WM's - they're easier and more efficient to use than their mouse-based counterparts.
Consider that mobile phones use a similar approach by getting rid of the concept of windows and they are, by a long shot, easier for most people to get to grips with. Tiling is a similar concept except that more than one application is visible at the same time. The lack of a window stack helps. Navigating a big physical table covered with pieces of paper (i.e. all applications on the same layer, where the table split into segments - aka desktops) is infinitely easier for a human than a stack of paper (i.e. finding something in a binder or book is more annoying and slower).
You don't need a manual to figure out how to use a touchscreen or whatnot though, which is generally why they're preferred by the masses, despite being inferior.
The same thing applies to emacs and vim too - they're capable of mostly everything IDEs do and much more, but it's non-obvious how to do things without taking the time to learn, read, search - something that people are less likely to do with age - but kids don't have a problem learning.
There's other issues like consistency too. With stacking based UIs you have some consistency built in, but you don't necessarily have it with the tiling window manager and minimal UI applications - take for example the difference in keybindings between xmonad and emacs. Another problem is that some apps can "hijack" your WM keybindings.
You can fix those issues by modifying the configs, but that's an even further level of learning that most people have no chance of ever doing.
There should be a formalised standard for keyboard based navigation. In fact, two standards might be a better approach - vi-like and emacs-like, since each of them caters to one of the major ways that people think. Having said that, with a little bit of work, you can get most of your daily applications to use vi keybindings (plugins for FF, Thunderbird and Chrome, Vim itself, custom keybindings for the WM, vi-mode for Zsh - in combination they create a programmer's version of Zen).
Thinking about it, I wonder if peoples' preference for these things might come down to their personality type - http://en.wikipedia.org/wiki/Myers-Briggs_Type_Indicator I'm not aware of any studies attempting to draw correlations between these things but, given how predictable people can be, it wouldn't surprise me if they existed.
>You can fix those issues by modifying the configs, but that's an even further level of learning that most people have no chance of ever doing.
When it comes down to it, the current generation of hardcore tiling WM's are experimental prototypes paving the way for the desktops of tomorrow. Just as many aspects of functional programming are seeping into popular languages, so tiling window management is seeping into popular desktops. I don't know about OS X but Windows 7, Gnome and KDE all support dragging a window's titlebar to the left-most or right-most edge of the screen to vertically tile it. It's extremely basic but it's an obvious influence.
Rather than a standard, we need a better API abstraction for keybinding, where users can control their keybindings from a single point, and it'll affect all their apps at once. App developers shouldn't tie functionality to specific keys, but to some abstract keys which the user controls.
I use Dvorak layout, but I generally prefer the conventional key locations for common tasks. So for example, cua-mode in emacs, I expect undo/cut/copy/paste to be in the locations of z,x,c,v on qwerty, except they're ;qjk on dvorak. It's awkward to make each app support this configuration - particularly when they all require a different language to configure.
Also, when a user configures his layout, he should be able to specify whether individual applications can override those keybindings or not - apps should request key combinations rather than assume they're available.
---
The personality types is an interesting thought, but I don't think it's really a big deal, because if you can't predict people, you just need to set a trend and make them predictable :p.
The editor wars are really blown out of proportion because of popularity or fashion rather than their technical merits. People are emotionally attached to their tools and aren't interested in the other anyway. I mean, who has the time to learn both emacs and vi enough to compare them objectively anyway? I've not used vi enough to really assess it's capabilities.
Maybe the personality type could give an indicator of a default setting for developers to put in. I'd be surprised if there's no research in this area, considering every desktop developer claims "we're building what users want after conducting usability tests." (I'd like to know who the audience for GNOME's testing was.)
---
I do hope tiling features will make it into desktop systems. Bluetile is an interesting example for gnome integration, although completely broken for gnome3.
Another interesting app is Opera. Their tabs have been based on MDI since day one (mid 90s). It basically has it's own internal WM, which includes some tiling features. (Opera's initial tabs were really tiles before they became the tabs we all know now.)
I think the other desktop environments are a bit slow on the takeup with tiling, and it's perhaps come to a grinding halt with the focus on tablets and touch now. We probably need to start experimenting with introducing touch into our tiling WMs to support heterogeneous inputs rather than exclusively keyboard too.
Probably the biggest joy about tiling WMs is that they're not some fixed system we're forced into using by the trendsetters, but they're more like APIs for developing your own personalized WM in. Until we build some customization abilities that don't require modifying code though, they probably won't become too popular - only minor features leaking into other systems.
(seriously.)
It's really very simple for a child. C-x C-s, C-x C-c, and arrow keys. All they really need to do.
I thought about vim, but I think it would lead to too many confusing situations.
I have a printed "cheat sheet" up there for the boys. It has commands and keyboard shortcuts. They sometimes forget it exists, but at least Jacob can read and follow directions on it without any trouble.
I wish I became familiar with emacs a lot earlier. It took me ages to transition from using IDEs because of the steep learning curve.
Oh, and I wish I grew up with a Dvorak keyboard. I was forced to learn it after getting RSI about 8 years ago - but I'm better for it now.
You ever tried creating something on the iPad?
Have you?
The "iPad is a consumption only device" meme needs to die. It's completely, totatally wrong.
That lack of featurism causes app developers to reinvent lots of basic stuff in their apps to get all the features they want. And sure, that happens on PCs too - but to a far lesser extent.
If you're familiar with the unix philosophy of making apps as filters, making them do one thing, and do it well - you'll understand how productive it can make you - and how there's no chance of reproducing that on a (non jailbroken) iPad.
And yes, I wasn't referring to art, but the software itself. Try creating an iPad app purely on the iPad - I wish you luck.
On the other hand , describing the iPad as a good computer for application development because you can SSH to a remote server and run VIM seems a little stretched, by that standard the Nokia that I had in 2002 was a dev machine.
There's a reason that Apple continues to support and develop OSX.
Agree. Android phone, or iPad. Amazingly easy for kids to use.
I'm skeptical that teaching kids starting with a command line is always a good approach.
**** CBM BASIC V2 ****
3583 BYTES FREE
READY.
I learned that by telling things to the computer (via the keyboard), it would obey commands or remember information. This actually isn't terribly hard for a kid to grasp, though this level of sophistication probably won't work with a kid who's much younger than 5 or 6.My son was two when he could operate the ipad, go to youtube find his movie. That's not because he could read or knew what he was doing, but because he had learned to mimic how I did things.
So the kids might learn the commands and there might be a lot of value in that. But I do not believe that they are actually internalizing and learning fundamentals in any intelectual sense.
Anyway it's kind of a hard subject. I think it's great what the OP is doing but I fear he is reading a little too much into the reaction from the kids. Unless of course they are gifted with a high IQ (which might very well be the case)
I have to respectfully disagree with you on this point. A member of my extended family does extensive work with deaf young children (aged six months to six years). Her job is to accelerate their spoken-language development, which has been delayed by virtue of being deaf. She repeatedly makes the point to me that the difference between children with delayed language (e.g. most of those she works with) and a "normal" child is that those with delayed language tend to not understand (or use) abstractions in their speech. They treat each word as if it has a single application or use. Once they understand that each word actually can have multiple applications, their ability to learn new words grows exponentially. Until that point, they are simply mimicking.
That sounds like an abstract fundamental to me, though I am perhaps mistaken. (This is also subject to a counter-argument about the nature/nurture aspect of language, e.g. do we have an inborn understanding of language.)
Also, on a more personal note: by the time I was five, I was experimenting with electrical circuits. A few 1.5V flashlight bulbs, a pair of switches, a few D-cell batteries, and some wire went a long way. I taught myself that you couldn't put lightbulbs after each other and have them light up to the same brightness (e.g. series resistance), but that you could connect them in parallel without any of those effects (these were short-term, so I didn't notice the extra power draw). Likewise for switches -- if they were in parallel, then breaking one was enough to break the entire circuit. Those are brand-new, abstract concepts that I was, as you say, internalizing in an intellectual sense.
And no, I wouldn't have called my IQ particularly high at the time, and I still would not.
I am not saying there is no understanding going on at all. What I am saying is that when my son uses the iPad or iPhone he does not know what the different things mean (i.e. he can't read that it says Video) he just knows what it do when he presses the icon.
I can't say to him:
"Find the LinkedIn application"
Only if I have done that a couple of times in front of him will he be able to.
With regards to the discussion about language, then yes that is a very complex discusion :)
My own theory is that we are born "pattern recognizing feedback loops" and thus our ability to recognize those patterns and recognize that we recognize them is the foundation of our ability to learn a language. Language is simply an abstraction of our natural ability to do symbolic manipulation.
It's like assembler (our basic symbolic manipulation skills) and the higher level languages (our more developed culturally inherited languages)
The fundamentals of language are getting pinned down at the same time in their little heads, and children who start training any skill at such an age tend to become proficient at it. I don't see why this can't be the case with computing as well.
And then it occurred to me: the perfect GUI for a child would be simply xmonad (a tiling window manager that can be controlled almost entirely by keyboard and has no need for mouse movements in most cases.
The perfect UI for a child and for all other people unfamiliar with a computer all in all is the touch screen.
The reason why the children have problems with the icons being too small and accidental dragging is because the mouse represents an extra layer of abstraction.
If you think about it your brain goes horisontal to vertical and not even in a one to one relationship.