Java is good for a starter class, since you can then branch easily into algorithms, OOP garbage and into real programming.
There's no excuse for using Java after that unless you are in a machine with only the JVM+JDK installed and need to make a simple TCP client/server toy in under 5 minutes.
>>6
Nobody has bothered doing it. The first JVM was done in C and so, it makes sense to just continue working on what is already known and understood.
Name:
Anonymous2012-11-05 7:38
>>11 Nobody has bothered doing it. The first JVM was done in C
Are you trying to CURTAIL MY ESSENTIAL RIGHTS cretin? Fuck off and die in a fire, I am entitled to my rights and I will fight for them.
and so, it makes sense to just continue working on what is already known and understood.
You asked for it. I am loading the gun right now, illogical piece of shit.
>>1
"Why?" is a useless question. "When?" is a better one. If you're writing a daemon that runs indefinitely and churns through a lot of data for every incoming connection, there's probably no reason at all to pick C over Java. However, if you're writing a frequently invoked command line tool that needs to launch and finish its task as quickly as possible, anything on the JVM is outright disqualified, whereas (ironically enough) Ruby or Perl might be as good a choice as C.
If you hope to be a good programmer you should learn all of these and know their weaknesses.
Name:
xposter2012-11-05 15:37
Here is something that always bothered me: What if there wouldn't be a single light source in the entire universe? Certainly it wouldn't be dark, because for there to be shadow you have to have a light source. On the other hand, if in such a universe you'd place a light source inside a closed box, the entire universe would be dark, because the box would effectively emit shadow into each direction.
>>25
There are lots of good reasons to pick C in the case you've presented. For one you can prove that what you wrote is correct, which is extremely important for what I'm currently working on. Incidentally, it's a series of daemons that will be invoked multiple times and then kept alive while a controller load-balances incoming connections over them. Very microkernel-esque.
Name:
Anonymous2012-11-05 18:08
>>29
I have to agree. A strongly typed language is invaluable when doing any kind of data processing. The compiler should go as far as running tests on your code to prove its correctness. Java simply doesn't give you that kind of guarantee.
You have memory safety for one. You can at least catch a generic exception at the base of root routine and restart the application and log a stack trace if something terrible happens. That's better than the segfault (at best) or memory corruption (at worst) that comes with C and C++. It's not the as good as an application that is proven correct, but there are static code analysis tools for that.
If >>30 is talking about an actually strongly typed language, then I would partially agree. But if >>30 is talking about C or C++ that then >>30 should join >>29 and >>25 in going back to /g/ and continue spreading their ignorance there.
>>33 You have memory safety for one. You can at least catch a generic exception at the base of root routine and restart the application and log a stack trace if something terrible happens.
That isn't even remotely ``memory safety''.
Name:
Anonymous2012-11-06 4:17
>>33
The whole discussion is about C/C++. Can't you read?
>>34
Give me your definition of memory safety. A Java program is not capable of producing an invalid memory access. Arbitrary memory corruption cannot happen. Although this is assuming the standard library is secure, which it isn't.
Neither C nor C++ are strongly typed. Now go back to /g/.
Name:
Anonymous2012-11-06 4:25
>>30
-i've done lots of data processing with perl specially when working with huuuge text files. hashtables (those things starting with %) might not be the faster thing out there but it's speed is pretty decent compared to the simplicity they offer to group data.
-i worked in a bank where perl was used to process data too, even to perform multidimensional calculations (risk curves with montecarlo data) in combination with a few c programs for critical parts.
-bioperl is still popular between researchers
as for java vs c, doesn't make much sense to compare the two. java vs c++ is more appropiate i think
Java pretends to be safe but it really isn't. Just because it forbids some operations with pointers and checks array bounds doesn't mean it'll save your sorry ass.
Since it's inexpressive as fuck too and is the epitome of "OOP for the sake of it" with an abhorrent standard library, it's difficult to justify choosing it for reasons other that not knowing any better.
The only reason to ever use Java is if you're a [b][i]TURNKEY SCALABLE ARCHITECTURE 2.0 AGILE ENTERPRISE DYNAMIC NIGGER AUTISTIC FEMINIST TRANSGENDER CORPORATE SOLUTIONS CODE MONKEY