why? Orion didn't die, it's still in reasonably wide use, and it's better than OC4J. Oracle took Orion and integrated it with their crap tech stack. The only real problem with Orion is that development on it has slowed down big-time, but it's still very stable and very usable.
While you have a good point, nothing in the world would ever change if everybody did that. It's better to try to make a stand first, outlining your exact reasons, and then leave. At least then you can say you've tried.
my main point is to do with things like distributed transactions, etc.
the comment on scalability and thread-safety was in response to a post way up above implying you needed to be an "uber-organization" to have those requirements.
i'm sick of all the ppl on slashdot flaming J2EE just because they don't understand the problems that need to be solved in the real world.
and u don't need to be some "uber-organization" to need scalability and thread-safety -- every system i've ever worked on has needed these and could never be done in LAMP.
Link 3 does not suggest that HT with Java requires special consideration when coding. It just implies that the application this person written had synchronisation issues that would only surface on a multi-CPU box, or a single CPU with HT enabled.
This just means that their application is incorrect and not at all thread safe, but you can "get away with it" on a single CPU where the particular race condition either never occurs, or is much much less likely to occur.
You have a good point, and in an ideal world driving to the conditions would be better than adhering to some arbitrary speed limit.
The thing is, speed is quantative and very easy to measure. Determining if somebody is driving safely for the current conditions is subjective and too hard to police.
While this is all true, and I agree, there are a great many more cats (etc) than there are wind turbines. If wind power was rolled out on a much larger scale, the amount of bird deaths would increase appropriately.
why? Orion didn't die, it's still in reasonably wide use, and it's better than OC4J. Oracle took Orion and integrated it with their crap tech stack. The only real problem with Orion is that development on it has slowed down big-time, but it's still very stable and very usable.
Oracle gives *less* than cost of living, they give nothing .. they promote you but keep you on a graduate salary.
Woops sorry do I sound bitter? Well, I only lasted 2.5 years being treated like that..
While you have a good point, nothing in the world would ever change if everybody did that. It's better to try to make a stand first, outlining your exact reasons, and then leave. At least then you can say you've tried.
absolutely :)
actually fair point, u probably can...
my main point is to do with things like distributed transactions, etc.
the comment on scalability and thread-safety was in response to a post way up above implying you needed to be an "uber-organization" to have those requirements.
hear, hear!
i'm sick of all the ppl on slashdot flaming J2EE just because they don't understand the problems that need to be solved in the real world.
and u don't need to be some "uber-organization" to need scalability and thread-safety -- every system i've ever worked on has needed these and could never be done in LAMP.
It was there you nong. But yes, it is a good one.
"This is one area where Linux is (rather far) behind Windows and OS X"
... Linux is not behind, it's just that Windows and OS X are not available in a large number of distributions, and are not as configurable.
ummm
aww man... i didn't, i had the new inventors on but my other half called me while it was on (doh!) and i missed most of it.
who won?
"Curiosity! do-do-de-dooo"
Oh how I miss that.
Link 3 does not suggest that HT with Java requires special consideration when coding. It just implies that the application this person written had synchronisation issues that would only surface on a multi-CPU box, or a single CPU with HT enabled.
This just means that their application is incorrect and not at all thread safe, but you can "get away with it" on a single CPU where the particular race condition either never occurs, or is much much less likely to occur.
Well, yeah, you know .. I can't hear your tone of voice over the internet, so some kind of marker is usually required to pick up sarcasm.
Sorry for not having the kind of telepathic intelligence you expect from slashdot readers.
morally reprehensible? ok ok we shouldn't even go here, but get off your high moral horse.
You have a good point, and in an ideal world driving to the conditions would be better than adhering to some arbitrary speed limit.
The thing is, speed is quantative and very easy to measure. Determining if somebody is driving safely for the current conditions is subjective and too hard to police.
Speeding is a problem for cyclists and pedestrians who have to share the roads with impatient maniacs.
ummm
that is at once truly paranoic and utterly brilliant.
with the server on earth?
dang that latency.
Yeah, I was very very scared for a minute.
Universal Product Code codes?
With sea urchin roe?
Wasabi?
hrmm.
You philistine!
China does it too. But then again, you probably just meant "The US is essentially the only country in the world ".
Yanks works fine with me.
While this is all true, and I agree, there are a great many more cats (etc) than there are wind turbines. If wind power was rolled out on a much larger scale, the amount of bird deaths would increase appropriately.
Still not a big issue IMO, just pointing it out.