Indeed. It *tried* to make it a hattrick with threading, but I haven't met anyone yet who groks threads any better in Java than they do in any other language. In other words, either they get threads, or they don't, regardless of the language used.
But oy, the bytecodes... the bytecodes... so close, and yet so... well no, really, just so far. Ick. Shoulda stuck with the toasters on that one.
It's actually worse than that. If you look really closely at J2EE you will notice that the *whole* Servlet spec is basically designed to take threads out of the developers hands. The container handles your threads for you. In fact it is a violation of the spec to spawn a thread inside a servlet on your own.
Face it, most folks aren't up to dining with philosophers, it's better to play airplane with them than have them (or someone else at the table) starve.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
1) It introduced Exceptions into common parlance
2) It introduced Interfaces into common parlance
no subject
But oy, the bytecodes... the bytecodes... so close, and yet so... well no, really, just so far. Ick. Shoulda stuck with the toasters on that one.
no subject
Face it, most folks aren't up to dining with philosophers, it's better to play airplane with them than have them (or someone else at the table) starve.
no subject
;-)
i've been thinking alot about analogies and counter-analogies
word-play as sword-play...
i'll explain later - feeling a bit too manic for coherent words right now.
but it's all good!!
:-D