Slashdot Mirror
Gosling Returns To The Java Fold
MemRaven writes "In an article on CNet News, James Gosling reveals that he's returning to the Java Tools group at Sun. The article touches briefly on the Eclipse situation as well as some vague statements about what he's doing in the future. Since he's been gone from the Java fold for a while, this might spell some definite changes in how Sun treats its stepchild."
there's nothing Sun can do about it. Gosling's comments about a developer perspective says it all. This is why eclipse has gained such a great following. I know from first hand, a large percentage of jakarta developers are strickly using eclipse now. If you ask around, the Tomcat developers for the most part use eclipse. Many other jakarta projects use eclipse exclusively.
Except that it's a monster, jaw-dropping, astounding flaw.
The Java Language Specification explicity states that using longs as an array index is an error. There might be a good reason for this, as there were 64-bit CPUs around when Java was being developed.
Also, when an array gets to a point of literally being 4,000,000,000 elements long, perhaps the application really could use some re-work. What applications need such large one-dimensional structures, anyway? Now that I think about it, it would be pretty easy to create larger arrays, anyway, in the way UNIX inodes allow indirection to access terabytes of data. The performance penalty of the indirection isn't huge.
I thought "Java" was supposed to be write-once, run any-damned-where you please.
It is. However, when you move forward to 64-bit address spaces--and use them--it makes going back to 32-bit a little difficult.
And you guys think Redmond's marketing department lies out their [collective] ass...
Actually, Sun is pretty straight-forward about Java. Usually, the lies come out of the mouths of the people who want to believe them.
Vote in November. You won't regret it.