View Full Version : Java in 2004
03-01-2004, 01:17 PM
I love Java, but I don't make games with it. Yet. C++ could learn a lot from it (and Visual Studio could learn a lot from Eclipse (http://www.eclipse.org)).
It's taught me a lot about object oriented design, and being an old C programmer, I was stuck in procedural mode. So learning Java really helped force me to begin thinking in objects instead of functions. And, perhaps ironically, that improved my C++ skills a lot.
I would probably make games with it, but for now there aren't enough "middleware" options (engines/frameworks/etc) for game development. There are plenty for C++, so that's what I'm doing.
One interesting possibility is to use JNI to hook a C++ engine with Java, and that might prove to be a good thing. But I have to get some revenue flowing before I can do R&D like that.
I am also interested in exploring managed C++ under .NET, but that kind of rules out simple ports to Mac and Linux, doesn't it?
07-30-2004, 03:54 AM
In a cruel twist of irony, the Java 1.5beta2 I have installed here won't even run my own damned games - some sort of daft socket error. That'll teach me for using beta software.
We're looking at donations (http://www.puppygames.net/forums/viewtopic.php?t=646) to buy a Mac for Elias to make the Mac port. That's all the bases covered pretty much. Anyone got a few bucks to donate? Everything gratefully received.
(Anyone else seen this:
java.io.IOException: Stream closed.
at java.net.PlainSocketImpl.available(Unknown Source)
at java.net.SocketInputStream.available(Unknown Source)
at java.io.BufferedInputStream.available(Unknown Source)
at sun.net.www.MeteredStream.available(Unknown Source)
at sun.net.www.http.KeepAliveStream.close(Unknown Source)
at java.io.FilterInputStream.close(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection$HttpIn putStream.close(Unknown Source)
at java.io.BufferedInputStream.close(Unknown Source)
at java.io.BufferedInputStream.close(Unknown Source)
at com.sun.javaws.net.BasicDownloadLayer.download(Unk nown Source)
at com.sun.javaws.cache.DownloadProtocol$RetrieveActi on.actionDownload(Unknown Source)
at com.sun.javaws.cache.DownloadProtocol.doDownload(U nknown Source)
at com.sun.javaws.cache.DownloadProtocol.getResource( Unknown Source)
at com.sun.javaws.LaunchDownload.downloadJarFiles(Unk nown Source)
at com.sun.javaws.LaunchDownload.downloadEagerorAll(U nknown Source)
at com.sun.javaws.Launcher.downloadResources(Unknown Source)
at com.sun.javaws.Launcher.handleApplicationDesc(Unkn own Source)
at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
07-30-2004, 04:02 AM
It is an interesting language / platform. In the list below, the cons outweigh the pros, but don't take that as an indictment of the language.
as a developer, I find it more productive than C++
there's no need to reinvent the wheel
write-once run-anywhere is marketing nonsense
the JRE download for end users is off-putting. If Sun allowed cut down distributions (maybe they do now) then that would be better
JWS is a pain in the butt if you upgrade your JRE
My overriding need, having limited time, was to find a language that allowed me to be productive. Java fulfilled that need, as I can write Java code around 2 to 3 times quicker than I can normally write C++. However, I've recently switched from Java to Python (using C/C++ where I need more speed) and found my productivity has improved - possibly up to a factor of 10 over C++.
If Python proves to be too slow then there's always Jython, which will allow me (amongst other things) to compile my Python code into Java bytecode, or if I feel the need to target .NET, IronPython.
07-30-2004, 05:15 AM
WORA did turn out to be marketing nonsense, mainly because of bugs and performance deficiencies. MacOS Java2D is still unusably slow. A couple of years ago we realised that it wasn't going to happen unless we made that LWJGL library do the work for us. By the end of the year we'll have WORA so long as 'A' stands for MacOS X, Win32, and Linux. Which covers all the major bases for indies. I am reasonably confident the palmsized gadget market will be able to run with LWJGL in 24-36 months time too.
07-30-2004, 07:14 AM
we use some JWS stuff at work, and Ive downloaded other stuff at home. personally i find it an unstable buggy mess, and would rather bathe in rotting beans than run a game or app that uses it.
Its hard enough assuming people have directx, java is a nightmare...
07-30-2004, 08:31 AM
Not in my experience - it depends if you want to write applets (and therefore rely on the rubbish that doesn't work properly) or target Java 1.4+ and use LWJGL :)
WORA would be really nice. Well, it's more like write once check for showstoppers anywere, but in most cases it just works (unless you did something silly and/or used BufferStrategy which is unfortunately somewhat relaxed under windows).
1.4.2 works pretty well imo. I also want to add something to Rod Hyde's pro and con list.
#one click download and install
#you can write games/applications which are really secure. There can't be a virus, trojan, adware, spyware, registry enties and no broken uninstallers which trash a whole directory without checking (one of Sierra's uninstallers did that - duh)
And for the cons:
Downloading DirectX, drivers, service packs is also off putting and the JRE is even smaller than those ati/nvidia graphic drivers.
JWS works pretty well since 1.4 (1.5 is somewhat broken, but it's beta right now).
Powered by vBulletin™ Version 4.1.3 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.