Only the Studio.
Server is standard C++ compiled on each platform. Robert From: Fogelson, Steve [mailto:[email protected]] Sent: Friday, October 22, 2010 4:49 PM To: [email protected] Subject: RE: Witango-Talk: Apple ceasing future distribution of Java.... Dumb question. Is the server component written in Java or just the studio? Steve Fogelson _____ From: Robert Garcia [mailto:[email protected]] Sent: Friday, October 22, 2010 12:50 PM To: [email protected] Subject: Re: Witango-Talk: Apple ceasing future distribution of Java.... Just my 2 cents, but we had to choose a write a few "run on all platforms" apps, and heavily looked at JAVA. In the end, we chose realbasic. You write in one language, it compiles natively to mac, windows, and linux. They have a huge development community now, and with new developments, I am sure will offer iphone development and such. I use Zend Studio, which is also java based. Whether on windows, or on the mac, I use it on both, it never feels like a fully native experience. Realbasic apps I have used do, just a thought. I remember talking to phil many moons ago about doing the studio in RB. At the time, I went through all it would need to do, and it fit, and RB is a much stronger platform now. Its not perfect, but it works. Don't worry, I am not suggesting you dump java and move to RB with v6, but I would be concerned about JAVA also, and now with this announcement, even more. Good idea to have a plan b in the works. -- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 15520 Coutelenc Rd Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [email protected] - [email protected] http://bighead.net/ - http://eventpix.com/ On Oct 22, 2010, at 9:49 AM, Robert Shubert wrote: Dale, This will actually have a HUGE impact on Witango. The version 6 studio is written completely in Java, and because Apple is such a pain when it comes to their Java implementation, there are chunks of the Studio which are branched or patched just to deal with Apple’s incomplete JVM. I’m very interested to see where this goes, if there is some support for it, it’ll be a pretty cool thing. If not, it could seriously hinder my development on the OS X platform. Between 2002 and 2005, it seemed like Java was going to be real programming force in the world. This was back when J2EE was becoming popular and the whole “Java 2” platform was coming out. Many thought that Java would be on equal footing, if not better, than other languages. It was, I believe, this reasoning that lead to the Witango J2EE deployment option and to the Studio being recreated as a Java application. Over the past 5 years though, Java has been somewhat standstill. Sure the newer platforms Java 5, Java 6, and soon Java 7 have been improvements throughout, but Apple sees their own Objective-C as the future, Microsoft is doing the same with C#, and Linux is steadfast with GCC. Java is certainly everywhere, and many developers love it, but it’s not really gaining any ground as the language of choice on any one platform. This is creating a problem with the level of integration that’s possible. Things like ODBC, window management, and task bars are some of the areas where the OSes keep moving forward and Java is left to catch up. I’m having to build native interfaces, per OS, to get some of the “niceties” to work properly. Just like everything, I suppose, Java has advantages and disadvantages. Robert From: Dale Graham [mailto:[email protected]] Sent: Friday, October 22, 2010 10:37 AM To: [email protected] Subject: Witango-Talk: Apple ceasing future distribution of Java.... Here's the story ... "Yesterday, Apple quietly announced that they would cease future distribution of their own custom Java packages, concerning some Java developers," John Brownlee reports for Cult of Mac. "So does that mean that Macs will no longer have up-to-date Java? A concerned Java Developer from Portico Systems emailed Steve Jobs, asking that very question." Jobs' response: Sun (now Oracle) supplies Java for all other platforms. They have their own release schedules, which are almost always different than ours, so the Java we ship is always a version behind. This may not be the best way to do it. Brownlee reports, "In other words, Apple’s leaving Java to the company that does it best… that is, if Oracle decides to step up and produce their own version of Java for Mac, as they do for every other platform. My guess is they will quickly fill the void and it’ll be a win for everyone." --------------------- If true, that's a great move ..... but my take is that I am concerned. We work with Oracle databases and know that Oracle has historically shown little or no interest in keeping parity for Mac OS X. I think it'll be even worse with their step-child, Java. Admittedly, this will probably have no impact on most of us on the Witango side, it's just an FYI. ___________________ Sent from my iPad 8) _____ To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body. _____ To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body. _____ To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body. _____ To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body.
