Either/or…
Either I fail at Java, or Java just simply fails.
To me, it’s as simple as that – no ifs, ands, or buts.
Today in Computer Science I was trying to create either a Fibonacci sequence generator/recursion experiment (Input nth term of Fibonacci sequence, program then spits it back out the correct number in the Fibonacci sequence) or a stopwatch/number incrementer (press start to start incrementing, press stop to stop incrementing, press restart to reset counter) – none of which worked!
Sure, I didn’t have all the necessary skills (how DO you differentiate between different buttons?), but for something to be considered good (therefore, not fail), I run it past this rule: if it’s sufficiently complicated enough for me to have to refer back to the textbook or included manual, then the developer/creator has made it too complicated. To be honest, those projects weren’t outside the scope of my knowledge, but they were challenging enough to make me think.
If I ever get those projects working, I’ll post back here.
Either that, or Cocoa/Objective-C for the win.