131–140 of 245 posts
I'm glad they didn't buy into the refcount meme that's so inexplicably popular these days.
http://www.cs.virginia.edu/%7Ecs415/reading/bacon-garbage.pd...
> Limited to 4tb heaps I can't believe the world we're living in, this is incredible. My first computer 512k of ram.
Earlier quoted context omitted.
> Our legal system is such that Oracle can still burn you down, even if you are right. Do you happen to know of any real-world case that's similar to the scenario you've described?
Google v Oracle comes to mind.
Earlier quoted context omitted.
It's just an object that lives on the stack, not the heap. In lots of languages when you create an object, it's pretty explicit where you're putting it. When Java was created, they wanted to get rid of that complexity, so primitives always go on the stack and objects always* go on the heap. * I think Java has escape analysis, which means that if it can determine that an object you created doesn't leave its context, i…
Moreover, they can be used in composite objects without pointer chasing. Suppose class A is a 32-byte value type. Then class B { A a1; A a2; } is one continuous 64-byte block of memory. Without value types, each A will be allocated separately on the heap, and B will be a pair of pointers. Lack of value types makes it hard to get cache efficient memory layouts in Java.
Earlier quoted context omitted.
You can also make a 3d game of large scale, and just let it have hiccups occasionally and still make a billion dollars. Of course those of us hosting servers for that particular game would have saved a ton of money and pain if they had not used Java, or used Java more cleverly.
The point is that they should have used Java more cleverly. One can make a game in C++ and make it just as bad.
Earlier quoted context omitted.
I did a search for "freecodyx user", and found no results, so I guess you don't exist.
In order for a meme to exist, it needs to be popular. A person doesn't need to be popular to exist. It's like you're claiming you are famous because your mom knows who you are.
Earlier quoted context omitted.
It's just an object that lives on the stack, not the heap. In lots of languages when you create an object, it's pretty explicit where you're putting it. When Java was created, they wanted to get rid of that complexity, so primitives always go on the stack and objects always* go on the heap. * I think Java has escape analysis, which means that if it can determine that an object you created doesn't leave its context, i…
It's more about the memory layout than where the objects live. For example, consider a Point class with (x, y) members. If you have an array of these, each element in the array will be a reference/pointer to a separately allocated Point instance which can be anywhere in the heap. Accessing the array is expensive due to lack of locality (arbitrary memory access). Additionally, each instance has substantial object over…
Earlier quoted context omitted.
I think a lack of value types also hurts Java significantly here. Though I believe they're also on the roadmap.
With generational GC, does this even matter? Generation 0 is pretty much a stack as far as performance and operation go.