Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Well like Tyler said, Java certainly doesnt produce trim fast code, so a Java based gempak will likely be a step backward in performance. Sorry if off topic a little.. Ray Weber MA Skywarn -----Original Message----- From: "Robert Mullenax" <Robert.Mullenax@xxxxxxxxxxxxx> To: "Tyler Allison" <tyler@xxxxxxxxxxxxxxxx>, "LDM-USERS" <ldm-users@xxxxxxxxxxxxxxxx> Date: Sun, 30 Mar 2008 05:28:51 -0500 Subject: Re: [ldm-users] user-stories for the LDM replacement Well another me, too I guess. Well, if panic is setting in over GEMPAK going away (or going to Java), the double panic for this. I don't want to sound ungrateful, but I can't imagine a worst decision than replacing LDM. Why must the computing world continually change and upgrade for the sake of change and upgrade? LDM is universally recognized as an incredibly stable and dependable program. Can Unidata provide information on who is seeking a replacement for LDM? Robert Mullenax CSBF/NMSU
ldm-users archives: