Slashdot Mirror

← Back to Stories (view on slashdot.org)

Quake2 Engine In Java

Posted by timothy on from the if-you-long-to-shoot-'em-up dept.

An anonymous reader writes "Ok, so the game is old and there was a really poor web version some years back, but some guys at Bytonic Software in Germany have done a full source port of the Quake2 engine from C to Java. It's cross platform, performs just about as fast as C and has room for further improvements according to the developer. Also, there was another game engine that ran Q3 maps that was shown recently at JavaOne. Are first generation Java games that far behind?"

5 of 123 comments (clear)

  1. What?! by Anonymous Coward · · Score: -1, Flamebait

    Have you actually tried it though? I did this morning and it's TERRIBLY slow. Their "just about as fast as C" comparison is WAY off.

    This isn't a troll, it's a fact. Check it out for yourself and see.

  2. Java != Slow, but that doesn't mean it's good. by Paradox · · Score: -1, Flamebait
    Maybe this will lay waste to claims that java is slow, bloated, and sucks.
    Java was never slow and bloated when compared to members of its own weight class. You may be tired of people saying "Java is slow!" but I'm even more tired of Java Developers parading this around, like they only not just found out about it. We're all happy for you folks. Welcome to the year 2001. Now, can we please start focusing on the real issues?
    I've only recently started doing heaving Java programming, and I have to say that the language is a dream to code with (provided you use a decent IDE).
    Ahh. Yes. Java, a dream to code with provided you use a decent IDE. Most people can code quite well with a 100 line elisp module to handle formatting, brace/paren matching and complile control. Java people needs the equivalent of a bustling shipyard with hundreds of dockworkers to move code around.

    Whizbang IDEs are nifty and all, but here's my feeling on it: if your language is so hard to work with that you require and IDE to develop and refactor in a reasonable amount of time/effort, then you do not have a language that is "a dream to code in." Having worked with Java, I'd say a powerful IDE like Eclipse is a requirement.

    It's not that these IDEs are bad! They're great, but they should be the icing on the cake. Your language should allready be usable pre-IDE.

    I'll take it over C++ any day, and MS's MFC is horrible on comparison.
    Not that I'm a huge C++ lover, but I have to say... you're right. It is a horrible comparison. MFC is the absolute worst environment in C++. Feel free to continue ignoring quality C++ tools for application development, like Qt, TAO, and the outright amazing Boost libraries.

    Sorry. Just because you can make a very old and relatively simple hardware-based game engine run in Java doesn't suddenly mean it doesn't suck. It still sucks, it's just that people are finally realizing why it sucks so badly (and it's not speed).

    --
    Slashdot. It's Not For Common Sense
  3. Re:Java != Slow by zangdesign · · Score: 1, Flamebait

    but Java isn't the turtle everyone makes it out to be.

    Until you run it on a 500-mHz iBook, don't make that claim.

    --
    To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
  4. Re:Java + C != Slow by Anonymous Coward · · Score: -1, Flamebait

    You're an idiot. J2SE doesn't come with APIs that access graphics and audio hardware. That's what the jogl and joal libraries are for. Are you going to claim that because the JRE is written in C, you have to include the "+ C" when you say that Java isn't slow?

  5. Re:Java != Slow by An+El+Haqq · · Score: 0, Flamebait

    Maybe this will lay waste to claims that java is slow, bloated, and sucks.

    Well, it may lay waste to claims that Java is slow, but I think it's hard to argue that it's not bloated. And, of course, Java does suck for rapid prototyping. However, it doesn't suck so much in other contexts.

    Mostly, I just wanted to type the word suck.