46 ms·
To be honest, I think that A) Literally everything is new to a kid, and if they can figure out how to play pokemon and minecraft, they can figure out what '||'
by empath75 10y ago
To be honest, I think that
A) Literally everything is new to a kid, and if they can figure out how to play pokemon and minecraft, they can figure out what '||' means.
B) Why teach them one way to do things and force them to relearn it a few years later?
- kibwen 10y ago> B) Why teach them one way to do things and force them > to relearn it a few years later? Who says anyone's being forced to relearn anything? My initial progression of languages went QuickBASIC -> Visual Basic -> Java, and despite the fact that Java is nothing like QuickBASIC the concepts helped me immensely in powering through Java's intimidating learning curve (i.e. "just type `public static class Hello { public static void main(String[] args) { system.out.println("Hello"); } }` for now (and for god's sake, make sure the file name is Hello.java), you'll understand what all that means in about six months or so"). It's easy to forget that our first exposure to programming involves a lot of fundamental concepts that are wholly incidental to the semantics of whatever language we're using. Trivial stuff like case sensitivity of identifiers (quite surprising to an enormous number of first-time programmers) as well as highly non-trivial stuff like setting up your programming environment and teaching people how to invoke the compiler/interpreter. Making the language itself small and intuitive, even if limited, goes a long way towards giving students a stone to cling to in the rushing river of unfamiliar concepts that they're being exposed to.
- kartickv 10y agoRegarding B, because starting them with a complex language may make many of them give up on programming completely.