Read a java spec bud. 'Like a cast in Java, declaring code as "unsafe" is equivalent to saying to the VM, "Hey, I know what I'm doing."' Huh? Java downcasts do not compromise the security of the VM.
It helps to be able to spell and use English grammar correctly -- in this sense, Slashdot is an exception. There were about 10-15 spelling/usage errors in your question, which lends an air of ignorance and stupidity to your online effort. At any rate, good luck for the future!
this is really not a disaster, since lutris products actually suck a whole lot. Believe me. Ugly, confused, disorganzied, buzzword-driven design. But here's jboss to save the day. Use it if you're doing server-side work in java.
It seems likely that in terms of market share, GNOME will eventually outrun KDE -- support from Sun and HP and from the (commercial ) eazel venture almost guarantee this.
What I find worrying is the fact that GNOME also benefits from a weird form of "open-source marketing" effect. By exploiting a hazy notion of political correctness, the GNOME folks, with strong backing from Red Hat, have cornered the market on GPL authenticity. As a result, thousands of well-intentioned users dutifully run a crappier desktop thinking they're doing the Right Thing. "Real" developers know the truth: KDE2 is more lucidly designed and implemented, and is miles ahead of GNOME, and nothing in GNOME's current plans will change that. Having written apps for both platforms, I now understand how it was possible for the KDE effort to generate KDevelop and Konqueror so quickly. I encourage skeptics to try Konqueror 2.1.
In the end, marketing will likely prevail. Leading to this analogy:
kde:gnome:: linux:windows
later
Can't say much about this -- apologies for being so mysterious -- but Linus' stubborn refusal to go for modern threads means that a certain group is actively extending a few core data structures and the scheduler to support a many-to-many threading model. Hint: these are people who've built this kind of thing before....
Slashdot Mirror
You're just pretending to be this stupid, right?
Read a java spec bud. 'Like a cast in Java, declaring code as "unsafe" is equivalent to saying to the VM, "Hey, I know what I'm doing."' Huh? Java downcasts do not compromise the security of the VM.
You can't spell worth shit, so it makes sense you were flagged as dangerous.
in most English-speaking countries it is metre, not meter.
Travel a little, see the world, learn a little...
It helps to be able to spell and use English grammar correctly -- in this sense, Slashdot is an exception. There were about 10-15 spelling/usage errors in your question, which lends an air of ignorance and stupidity to your online effort. At any rate, good luck for the future!
Why is it that British types so often can't spell worth a heck?
this is really not a disaster, since lutris products actually suck a whole lot. Believe me. Ugly, confused, disorganzied, buzzword-driven design. But here's jboss to save the day. Use it if you're doing server-side work in java.
in the U5s the 256K of L2 cache wasn't on the CPU die, and didn't run at full processor speed.
It seems likely that in terms of market share, GNOME will eventually outrun KDE -- support from Sun and HP and from the (commercial ) eazel venture almost guarantee this. What I find worrying is the fact that GNOME also benefits from a weird form of "open-source marketing" effect. By exploiting a hazy notion of political correctness, the GNOME folks, with strong backing from Red Hat, have cornered the market on GPL authenticity. As a result, thousands of well-intentioned users dutifully run a crappier desktop thinking they're doing the Right Thing. "Real" developers know the truth: KDE2 is more lucidly designed and implemented, and is miles ahead of GNOME, and nothing in GNOME's current plans will change that. Having written apps for both platforms, I now understand how it was possible for the KDE effort to generate KDevelop and Konqueror so quickly. I encourage skeptics to try Konqueror 2.1. In the end, marketing will likely prevail. Leading to this analogy: kde:gnome :: linux:windows
later
Can't say much about this -- apologies for being so mysterious -- but Linus' stubborn refusal to go for modern threads means that a certain group is actively extending a few core data structures and the scheduler to support a many-to-many threading model. Hint: these are people who've built this kind of thing before....
Went to the postgres site, downloads are only for linux, didn't see a source download. What gives? is it only supported on linux?
Well put.