Timeline for Criteria for selecting language for first programming course
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 25, 2013 at 18:12 | comment | added | vonbrand | The problem with OOP is that for the range of toy problems covered in the first year or so of programming it just gets in the way, without any clear advantage. OOP becomes important (and is appreciated) when your programs are a thousand lines or so. "Java without OOP" is horrible, lots of completely opaque stuff that "has to be written this way" goes against people learning, not parroting. | |
| May 28, 2012 at 5:30 | comment | added | Barry Brown |
A good IDE can defer public static void main() for a very long time. BlueJ is a good example of an IDE that lets students write programs without a single main anywhere in it.
|
|
| May 21, 2012 at 12:22 | comment | added | Dave Clarke |
@Raphael: It is impossible to avoid public static void main() in Java, which has to be within the context of some class. This makes Java less than ideal as a first language, though of course the hurdle isn't too great.
|
|
| May 21, 2012 at 8:10 | comment | added | Raphael | You can quite easily start with a subset of, say, Java first to show procedural style. Then you open up Pandora's box and show how the same stuff looks like with OOP. | |
| May 21, 2012 at 1:42 | history | answered | Nazar Merza | CC BY-SA 3.0 |