So now that this semester is over with, so is Statistics (worst part about that is that I don't even get an AP/Honors/College credit for taking it, so odds are I'll be doing the whole thing over again in college), anyway, this coming semester will have a Java/CAD course to replace the Statistics class. As most of you know, I already know the basic programming concepts. I also have used Java quite a bit. I am currently working on a GitHub app for Android (<plug>It's already on the Market and SlideME too, search for "Hubroid"</plug>), so I'm getting my fair share of Java practice in. Now, Android doesn't use the standard Java library for functions and the like, so do you think I should read up on those functions before I begin the course? I'm aware that we'll most likely go over basic stuff in the first week or so like how to initialize variables and create classes and stuff, but I just want to get ahead of the game.

Also, this new theme distracted me so much, I wandered off trying to find a post explaining it. I ended up closing the tab, only to reopen it to finally post this thing. Curse you Miah for exciting my ADD.

If your Java class is anything like the one I took in high school (AP CompSci?), I can safely say that you'll just want to review the way Java handles strings, arrays (as in the class, not the native sort) and other data structures (stacks, linked lists), and sorts (quick, merge, insertion and selection).

Unless they changed things in the past year or so.

Which they probably did.

-- Griffinhart

PS. If you're on Firefox, Lazarus. Dunno 'bout Chrome (I haven't really been following Chrome re: extensions/addons/whathaveyous... or anything else, really, for that matter).

You will be fine. It's a course, not a test. They will teach you the material before you'll be expected to use it. At least, they should. If you have any programming experience you should be just fine.

Thanks guys, I figured I was set for this, I will probably end up helping a few of my classmates with things.
If this is in regard to the whole closing the tab thing, I wasn't in the middle of writing the post. I simply entirely forgot my purpose for visiting.

I just noticed this post. All I have to say is this.

Java. Arrrrrrgh.

I forget. Why?

Because it's a poor language.

How so?

It lost all its money. The recession hit hard.

And that's all Jeff Goldblum has to say about Java.

But _why_ do you consider it poor? Is it the syntax? The core libraries? The speed?

Ignore them they are both C++ Dev's their heads are filled with custom hacks

The basics. It's a lobotomized language for people that don't want to think too hard. There are no pointers, a rather basic thing. You have to memorize bullshit drilldowns without adequate reason (it's not printf, it's System.out.printf). It's slow and bloated. It's a memory whore. It practically runs in a shell for god's sake. There's a millions reasons to not use it and only one that I can think of to use it, and that it if you can't figure out the basics of a real programming language.

Make no mistake. Java is not a programming language. What it is, is a scripting language. You can debate this all you want, but until Java doesn't require a special environment to run its programs in, the arguement stands on its own.

Okay, thanks for the real answer. I have no intentions on actually using Java any further than developing Android applications, so I'm glad I learned C/C++ before I even stepped foot in Java.

<plug>All you GitHub lovers, my app Hubroid is out on the Market, and I'm working on some really cool updates</plug>

Java is a classic case of design-by-committee. It's not actually as slow as many would have you believe, but it is a memory hog. The real problems, however, are with the language itself. I disagree with Miah on pointers: they aren't necessary as long as the semantics of what's a copy and what's a reference are clear. In Java this is not the case: my blog post on the matter.

And don't be misled by the terms programming vs scripting, see this blog post this time