EmuCR Feeds
Email Us

EmuCR:JPcspJpcsp SVN r2126 is released. JPCSP is a PlayStation Portable(PSP) emulator which is written in JAVA. JPCSP is the first PSP emulator that is written in JAVA. Most people think java is too slow. But Shadow and his team has proven us wrong. The newest Java versions are almost as fast as C which makes it very interesting for emu dev's. Shadow and his team are working day and night with pleasure on the emu, many coders have dedicated to the project. Because it's written in java many young devs find it interesting to learn how the emulator works.

Jpcsp SVN changelog:
r2126
Further network improvements: implemented sceNetInetPoll. Small fix in sceNetInetSelect.

Download: Jpcsp SVN r2126
Source: Here

8 Comments:

  1. I wonder when this emu is gonna be abble tu run games at decent speed, better not trow away my brick for the next 10 years ;'(

    ReplyDelete
  2. Then stop complaint and play them on your psp instead.

    ReplyDelete
  3. It's going to run at decent speed when it gets coded in an actual language and not a horrible one like Java.

    ReplyDelete
  4. Yeah, Java is simply too slow for emulation of powerful systems. We'd either have to wait for someone to code a PSP emu using a more optimized language (PCSP seems to be progressing slower than jpcsp since it's not open source) or wait until PCs become fast enough (which could be a long ways off)

    ReplyDelete
  5. Why evryone think Java is slow. Thats no more so!
    Sometimes can java work even fast or faster then C++
    look at:
    http://scribblethink.org/Computer/javaCbenchmark.html

    ReplyDelete
  6. Yeah, Erzesel, sure...Java isn't faster than C++...it's just C++ have trash OOP impl. and that's all.

    Interpretation will never be faster than native. You can continue to live in your dream world.

    ReplyDelete
  7. Most JVMs are capable of compiling Java byte-code into native machine code, instead of using the interpreter. This is done through a process called JIT (Just-in-time compiling), or through the process of Dynamic Recompilation. JIT also allows the code to be optimized as it runs (which is what Sun's JVM does, I believe). The native code could possibly be cached for later executions, but I'm not sure of that.

    Whether programs written in Java and having their byte-code JIT/DRC compiled into native code, or programs written in C++ and compiled into native code are faster is a matter of debate. I sincerely doubt that Jpcsp is run interpreted, otherwise the JVM could just use JIT compiling and gain a large speed boost.

    There are many features in Java that COULD make it slower. This article gives some examples:
    http://www.jelovic.com/articles/why_java_is_slow.htm
    But that article assumes its points can't be addressed (for example, its 'all objects are allocated on the heap' point can be addressed with object pools).

    I think we can walk away from this with the understanding that programs written in Java are not obscenely slower than ones written in C++. Benchmarks show that, depending on certain factors, programs can perform faster or slower, and I doubt you would see a huge difference in performance if Jpcsp was written in C/C++. And don't forget, it's still possible to run libraries written in C/C++ in Java code.

    ReplyDelete
  8. monster hunter is lame I say man

    ReplyDelete

Can't post a comment? Try This!