|
But is it any simpler than other more open-ended tools? Python+pygame is really popular for prototyping little game ideas, for instance. I think the point about choosing Processing, for most people, is the simple and well-established path to do: 1 - graphic-oriented apps 2 - stuff that can run in the browser (although Java applets are a massive PITA, sadly, and are slowly but steadily being phased out) 3 - not much else (actual feature: the excess of choice is overwhelming for a beginner) And then I have this concern that many students, when already proficient in an "introductory language" never quite find the motivation to jump to another language with significantly different structure and syntax. Since proficiency in an introductory language is achieved rather early, it becomes a dead end before they can develop a "real taste" for advanced programming. This has happened to a lot of people I know. Many of my friends started in the 80s with Sinclair BASIC or some other BASIC (C64, C128, Oric, MSX, etc). These have, for the most part, enough built-in graphic primitives to toy around a lot and make simple games with little experience, even with the limited hardware of the time. But then, the next step in order to overcome these nice but slow interpreters was usually assembly or complex compiled languages (usually proprietary implementations, expensive and with obscure support). So they stopped right there. It's not so bad now but the wall is still there. |