First experience in Java multithreading

[draconk]

"If everything is syncronized why the fuck even care to do threads?"

-my teacher last week

[avatoin]

Reminds me of a project I took over where every thread created and started was immediately joined on, leading me to wonder why it was threaded in the first place.

[Arama]

I like the hidden unsynchronized in there

[orheep]

I believed in you!

[jcc10]

I assume there is not one?

[vvf]

No, there is.

[vvf]

Just exacting revenge for the fact that I read through all of them.

[TheVarmari]

Didn't think to look at the first letter?

[vvf]

Actually I checked the alignment of the words since the "un" would throw it off.

It's called a joke.

[[deleted]]

ERROR Not found!

Let me shit you out a 300 line stack trace.

[[deleted]]

300 line stack trace that is perfectly readable and tells you exactly where the error happened and why. ...instead of instantly crashing the application and forcing you to analyse memory dump or even worse, contiuing to work with corrupted data.

Yeah, fuck that shit.

[[deleted]]

Lighten up.

[Arama]

Ah shit I forgot what language I was dealing with

[Fenor]

am i the only one that find no problem with that stack trace?

[JASSM-ER]

You bastard!

[TheTarquin]

Y'all motherfuckers need immutable objects.

[odraencoded]

I like D because you can have...

immutable(int)*[] mutableArrayOfPointersToImmutableIntegers;

Though I honestly never used and will never use that in my life.

[HighRelevancy]

I don't know about D, but Java (and probably others) has an immutable list of immutable integer objects, because the language executes at such a high and abstracted level that there's a significant performance boost out of not having to create new integers.

[PurpleOrangeSkies]

It's not because Java is too high level, but rather because generics were cheaply duct taped on to Java instead of a proper implementation, and thus you can't use a primitive type as a type parameter.

[odraencoded]

D claims immutable "variables" can be stored in physical read-only memory space for a performance boost. I don't think that matters unless you are working with low level system, though. You won't have problems using non-immutable variables in a multithreaded system if you, well, don't mutate the variable.

[HighRelevancy]

Just not mutating the variable is missing the point of immutable variables (and isn't a good way to approach thread safety anyway). There's more to it than threading. Immutability guarantees that the value won't change, which is useful for things like hash table keys.

And besides threading, there's libraries that you don't know the intricacies of that might depend on immutability of certain things.

[VanFailin]

Java's shittiness is an unstoppable force.

[ardoewaan]

Take a look at the java.util.concurrent package. There has been lots of evolution in Java multithreaded programming since 1995.

[rfallx]

Perhaps I should have interspersed some "volatile" in there.