This is not a problem on most jvms that I've had experience with. On windows sun's jvm has no problem with multi procs (I assume it's no different with multi cores). And yes, you need native threads to spread across processors. I believe that, at least in the sun linux jdk, java threads go 1:1 with posix threads. Wouldn't surprise me if osxs situation is somewhat different. I've never been terribly impressed with its speed (although I'm still using a G4).Originally posted by: AmigaMan
As a senior java dev myself, let me just say, that's a pretty nice machine. However, I've found that several things help me out more than others. Dual cores are nice for multitasking, but due to how Java works, multithreading on several cores is not feasible. I've heard some debate on native java threads that allow themsevles to be real threads on the OS, but I'm not sure how that's handled by the JVM.
AbsolutelyAnother thing is dual monitors are a must and the more the merrier. I have a laptop I do all my development on and it's connected via DVI to an external 20" Dell LCD. Usually my IDE is on the external LCD and everything else (browser, email client, shells) are on the laptop. Having a large monitor to display as much code as possible just can't be beat.
I concur. Pretty much any j2ee server will eat memory like crazy and it gets pretty bad when you throw in multiple instances, a database, eclipse and, in your case, another entire operating system This is absolutely where I'd throw money with the least hesitation.Finally, depending on the type of development you do, you'll need more than 2GB of memory. I have 2GB and I tend to wish I had more. Especially when you start up more than one instance of Weblogic, have several browsers open, running Eclipse, and running Parallels (so I can see my stuff in Windows). That 2GB becomes used up in a heartbeat. An extra 1GB would give me some breathing room, but I'd want 4GB (but too bad my MacBookPro can't take more than 3GB).
I concur againI also didn't see anything about a HD? In my case, I'd rather have fast over space. Some 15K SCSI drives would be awesome since compiling code tends to thrash the HD a lot.
As a senior java dev myself, let me just say, that's a pretty nice machine. However, I've found that several things help me out more than others. Dual cores are nice for multitasking, but due to how Java works, multithreading on several cores is not feasible. I've heard some debate on native java threads that allow themsevles to be real threads on the OS, but I'm not sure how that's handled by the JVM.
Originally posted by: Argo
As a senior java dev myself, let me just say, that's a pretty nice machine. However, I've found that several things help me out more than others. Dual cores are nice for multitasking, but due to how Java works, multithreading on several cores is not feasible. I've heard some debate on native java threads that allow themsevles to be real threads on the OS, but I'm not sure how that's handled by the JVM.
I'm not sure what you mean. Pretty much every JVM out there uses native OS threads. There were some older Linux 7.2 JVMs that didn't use green threads, but those were gone for quite some time now.
Originally posted by: tfinch2
Waste of money if you're doing just Java dev for college labs on it.
Originally posted by: aceO07
Originally posted by: tfinch2
Waste of money if you're doing just Java dev for college labs on it.
I agree. I could be wrong. What course are you buying it for?
If you're using it as an excuse to get a really nice setup, go for it.
Those were quite a pair of over-generalizations!Originally posted by: Cooler
If you?re writing a java application as long as you have about a 2 gig of ram and a cpu that less then 4 years old you will be fine. If you really need high levels of multy threading and fast possessing you should use C++ , FORTRAN, with some asm if needed.