What's the best beginner friendly language and why is it Java?
its C or x86 asm
Java is a clusterfuck with its this.mambo.jumbo(bla.bla, bla.lalala())
>>62339156Scanner reader = new Scanner(System.in);
int variable = reader.nextInt();
The answer is its library.
Go back to werk
BASIC and Forth and Smalltalk are the best beginner languages.
>>62339156
C or assembly. I'm serious. That's where everyone should start.
>>62339156
It's a beginner friendly language in the same way that an automatic Nissan Altima is a beginner friendly car. They might learn how to get from point A to point B, but they'll never truly learn how the car works because to them it's just a way to get somewhere.
C without pointers.
There's a ton of stuff to cover as a first language; Java, or any other OOP language, adds a ton of stuff that can wait.
If I were in charge of curriculum, it would look something like this for first course:
- assignments
- conditionals and a little bit of Boolean logic
- switch-case
- for, while, do-while loops, plus break and continue
- functions
- input from keyboard, command-line argument flags, and files
That's 16 weeks with plenty of time for assignments and practice, plus some buffer days (professor is sick, federal holiday, inclement weather.
Second course could be a continuation of C, to cover pointers, plus some OOP foundations in C++.
I would follow up in the third course with Java.
Java is such a massive language that I would recommend waiting until programming foundations are established before learning it.
Otherwise you get distracted with the vast amount of standard library classes.
>>62339669
>>62339718
>C
Nah, it's Pascal.
As low-level as C, but with a syntax that makes sense and doesn't turn type declarations into a recursive nightmare.
>>62339156
beginner friendly? it's too much of a clusterfuck for that
>>62340149
>Pascal
and then he'll enjoy relearning everything when he inevitably moves to a C-like language.
>>62340227
Just
#DEFINE begin {
#DEFINE end }
It'll be fine :^)
>>62339201
what is wrong?
>>62339718
>There's a ton of stuff to cover as a first language; Java, or any other OOP language, adds a ton of stuff that can wait.
My introductory course used Java, but for the first half treated like a procedural language, with everything happening in main. Then they started talking about objects and the like.
I found it was sensible way of doing things.