<p>C++ is kind of an intermediate between C and Java (in terms of low-level vs. high-level languages), so if you are going to learn both anyway, I might start with C++. C -> C++ -> Java seems like a very natural low-to-high progression (not that low-to-high is the only valid progression, but you've already started on it).</p>
<p>I find your school's curriculum structure a little odd, but that's beside the point.</p>
<p>Thanks everyone for your comments. I don't know which UC to transfer, but I'll apply for UCLA UCD UCI UCSD UCSB.</p>
<p>Hi everyone. I don't really know if Computer Science is the correct major for me. I want to learn about software and video games things. Do you think Computer Science will do it for me? Thanks in advance</p>
<p>Btw, can anyone tell me the big difference between Computer Science and Computer Science and Engineering?</p>
<p>If you're going to take both it really doesn't matter which one you start with but read the course descriptions to find if one is more of an intro class than the other and start with that one. Once you get into the CS major you'll most likely use both of them plus other languages. These languages are just a means to an end and you'll find that the language is less important than understanding the concepts behind the programming techniques/algorithms/etc.. </p>
<p>btw - Unless it's changed recently, UCSD starts with Java but you'll end up using C, C++, and other languages as well. UCLA starts with C/C++ but you'll end up using Java and others later. Outside of the intro classes (in whatever language), they likely won't even teach you the other languages - they'll expect you to be able to pick them up on your own while they're more focused on concepts (hence my 'means to an end statement').</p>
<p>Yes - CS majors are employed in the video game industry although the majority of grads will end up employed elsewhere. It's common for HS guys to select CS because they want to go into the video game business but most of them will see all the other opportunities and head into different industries. This isn't anything to worry about now.</p>
<p>JoeJoe read the article on "Joel on Software" and see what employers consider java schools. If your school teachers Java in CS1 and CS2 you are a java school. My school is and was a java school, but I didnt only learn java. Well I was only taught java and then we were left to ourselves to learn the list below. In the end. I had in all my classes become fluent in the following languages, </p>
<p>Java
C
C++
C#
prolog
Lisp
Scheme
ML
Erlang
Ruby
FORTRAN
Fortress
Mips Assembly
ARM Assembly
X86 Assembly</p>
<p>Even with that long list, my school is still considered a java school.</p>
<p>Also JoeJoe, I have many friends who are EE graduates and have field jobs. Many with Con Edison and the MTA here in NYC as well as National Grid.</p>
<p>I agree with Jessie here. I would take C++ first then take Java.</p>
<p>
[quote]
JoeJoe read the article on "Joel on Software" and see what employers consider java schools. If your school teachers Java in CS1 and CS2 you are a java school. My school is and was a java school, but I didnt only learn java. Well I was only taught java and then we were left to ourselves to learn the list below. In the end. I had in all my classes become fluent in the following languages, </p>
<p>Java
C
C++
C#
prolog
Lisp
Scheme
ML
Erlang
Ruby
FORTRAN
Fortress
Mips Assembly
ARM Assembly
X86 Assembly</p>
<p>Even with that long list, my school is still considered a java school.</p>
<p>Also JoeJoe, I have many friends who are EE graduates and have field jobs. Many with Con Edison and the MTA here in NYC as well as National Grid.
[/quote]
</p>
<p>I know the article you refer to. I even went back and reread it today because I'm positive you are taking the meaning of "Java school" slightly out of context. Teaching Java first year is not the only definition of a Java school. </p>
<p>
[quote]
Therein lies the debate. Years of whinging by lazy CS undergrads like me, combined with complaints from industry about how few CS majors are graduating from American universities, have taken a toll, and in the last decade a large number of otherwise perfectly good schools have gone 100% Java. It's hip, the recruiters who use "grep" to evaluate resumes seem to like it, and, best of all, there's nothing hard enough about Java to really weed out the programmers without the part of the brain that does pointers or recursion, so the drop-out rates are lower, and the computer science departments have more students, and bigger budgets, and all is well.</p>
<p>The lucky kids of JavaSchools are never going to get weird segfaults trying to implement pointer-based hash tables. They're never going to go stark, raving mad trying to pack things into bits. They'll never have to get their head around how, in a purely functional program, the value of a variable never changes, and yet, it changes all the time! A paradox!
[/quote]
</p>
<p>Anyways we're getting a little off topic here eh?</p>