I had previously used slack since 92, but gave up on it in release 12, where for some insane reason they decided to install a kernel you were not supposed to actually use. WTF? That coupled with the lack of a forum or mailing list made it more trouble that it was worth.
Since we don't know we're a sim, They must not want us to know. However, They allowed the matrix to be made (and a sequel no less) which causes us to question if we are a sim, which is contrary to what They want. Therefore it makes more sense, that since the matrix was made, that we are not a sim.
Of couse, maybe They know that we know that They know and this is all part of Their fiendish plan...
Even more efficient is to give your stringbuffer a resonable default size, this way it doesn't have to waste time + memory growing. This is true of many Objects in java that resize automagically as required. (ie Vector). I've not yet come across a situation where I couldn't estimate a good default size for these types of Objects.
There should be a way to moderate articles themselves (like posters comments) that way, if an article was modded to -10000 dupe, it wouldn't show up on my front page - if I'm logged in of course.
No. This is a good point. If you work in an environment where there are many different active streams then trying merge these types of changes could be quite difficult.
Often however, if you get back to 1 live development stream, this is where it might make sense to do some refactoring.
My ( basic ) understanding is that this is a quantum mechanical process. Right outside the
event horizon you get particle-antiparticle
creation. If memory serves the antiparticle is absorbed by the black hole ( reducing it's mass)
and the particle is emitted.
I've found this to be quite the oposite
actually. I've found it very difficult/
tedious to fix the memory leaks in java.
The only way I know of to find the leaks is
through 3rd party tools like JProbe. Once
you find them, you have to cleanup all the
references to the Object to make it
available for gc.
The tediousness comes when you have to
store all your listeners in member
variables and explicitly remove them
when you want your gui objects to go away.
(or something equally annoying)
Again though unless you have a very large
or very long running app you would be unlikely
to ever notice this. I believe the default
max java heap size is 16M.
Actualy, I don't mean that the VM can't figure
out if an object is dead or not. The problem arises as designers make design decisions without understnding the consequences.
The problem arises when, from the designers point
of view, the object will no longer be used, but from the VMs point of view, the object is still alive. An object that has a root parent in the
reference hierarchy will not be garbage collected.
Things I have seen that hold onto large object
trees are things like, anonymous innner classes
(implcit "this" reference), listeners on gui components not being removed, and static class
variables holding onto objects.
Java is a great programming language because it
is easy to use thanks to all the built in
stuff, but nothing is free. You generally pay
for it with performance and memory usage.
Here's an article discussing "memory leaks" in java
Actually, it is a misconception that java
doesn't suffer from memory leaks. Just because
it is garbage collected doesn't mean that
you don't have huge trees of objects that will
never get gc'd.
If you don't explicitly design in creation/destruction of your objects you will leak memory. For the average sized application it propably isn't noticeable, but if your app needs
to run for a long time, you will eventually run out of heap.
You are missing the point people. The icravetv story is simply consequential. The vitally inportant thing here is that someone thinks that television is intellectual property and not just the mindless rantings of madmen. Not only did someone say this, but the journalist felt the comment was worthy of a quote.
American broadcasters and sports leagues, who call it "one of the largest and most brazen thefts of intellectual property ever committed in the United States."
I know slashdot is doing a good job, because more and more of the items I read disturb me - like this one.
It will all balance out in the end. Some folks will have computers implanted in them, but they will be so busy having web pages rendered directly on their brain, that they won't notice the genetically altered 100 foot tall cockroaches that will stomp them to a pulp.
Don't worry in the end evolution will achieve a balance. The giant cockroaches will run out of netheads to chew on, and starve to death.
The benefit of returning the tiger to a viable population would be incalculable," said Don Colgan, head of the evolutionary biology department of the Australian Museum, which owns the pickled tiger. "It would be a triumph for Australian science."
Is anyone else concerned by the tone of the scientists involved? Well, if it brings prestige, then by all means - do whatever the heck you want. Ethics? We don't need no stinking ethics.
This sounds like the beginning of a bad B movie, which eventually involves a 500 foot genetically enhanced cockroach trashing New York and munching on the inhabitants.
I am saddened that humanity hasn't learned anything from the wisdon of Godzilla movies.
Slashdot Mirror
I had previously used slack since 92, but gave up on it in release 12, where for some insane reason they decided to install a kernel you were not supposed to actually use. WTF? That coupled with the lack of a forum or mailing list made it more trouble that it was worth.
Of couse, maybe They know that we know that They know and this is all part of Their fiendish plan...
Even more efficient is to give your stringbuffer a resonable default size, this way it doesn't have to waste time + memory growing. This is true of many Objects in java that resize automagically as required. (ie Vector). I've not yet come across a situation where I couldn't estimate a good default size for these types of Objects.
There should be a way to moderate articles themselves (like posters comments) that way, if
an article was modded to -10000 dupe, it wouldn't show up on my front page - if I'm logged in of course.
I agree. I find this annoying as well.
Often however, if you get back to 1 live development stream, this is where it might make sense to do some refactoring.
Perhaps because he's imbalanced?
event horizon you get particle-antiparticle
creation. If memory serves the antiparticle is absorbed by the black hole ( reducing it's mass)
and the particle is emitted.
http://wwwusr.obspm.fr/admin/seminaire/chalonge
So when is Pitfall going to be available on Linux?
The tediousness comes when you have to store all your listeners in member variables and explicitly remove them when you want your gui objects to go away. (or something equally annoying)
Again though unless you have a very large or very long running app you would be unlikely to ever notice this. I believe the default max java heap size is 16M.
The problem arises when, from the designers point of view, the object will no longer be used, but from the VMs point of view, the object is still alive. An object that has a root parent in the reference hierarchy will not be garbage collected.
Things I have seen that hold onto large object trees are things like, anonymous innner classes (implcit "this" reference), listeners on gui components not being removed, and static class variables holding onto objects.
Java is a great programming language because it is easy to use thanks to all the built in stuff, but nothing is free. You generally pay for it with performance and memory usage.
Here's an article discussing "memory leaks" in java
http://www.devx.com/upload/free/features/javapro/1 999/06jun99/tl0699/tl0699.asp
Actually, it is a misconception that java doesn't suffer from memory leaks. Just because it is garbage collected doesn't mean that you don't have huge trees of objects that will never get gc'd. If you don't explicitly design in creation/destruction of your objects you will leak memory. For the average sized application it propably isn't noticeable, but if your app needs to run for a long time, you will eventually run out of heap.
Don't worry in the end evolution will achieve a balance. The giant cockroaches will run out of netheads to chew on, and starve to death.
This sounds like the beginning of a bad B movie, which eventually involves a 500 foot genetically enhanced cockroach trashing New York and munching on the inhabitants.
I am saddened that humanity hasn't learned anything from the wisdon of Godzilla movies.