Allowing 32bit Java 1.8 on 64bit systems

Discussion in 'Client & Site Suggestions' started by Taric, Mar 24, 2015.

  1. By forcing 64bit java on us, you've made it a lot harder for us Simba users to use both RuneMate and Simba.
    (Simba only uses 32bit java.)

    If this is what you are going for, then by all means, keep it up. :p

    If you want to allow peace and prosperity between the two clients, however, then take away that blasted 64bit requirement nonsense!

    Stay Sexy
  2. To deliver the best experience possible we need to force a 64bit JRE on a 64bit OS. It results in a much more stable client.
  3. That sounds like something microsoft would say to get us to use Internet Explorer... :p

    FINE! I guess I'll just have to switch between the versions of Java... Sad face.
  4. There really is no other way to put it. By unlocking more of the RAM you have to the application it can scale its caching up and be far less CPU intensive. Given it's 2015, there's no excuse for vendors to only have 32bit support. We can't make concessions for others' shortcomings.
  5. Most people have to keep both 32 and 64 bit versions of Java anyway because Google Chrome can only use 32-bit.

    All you have to do really is update twice with every new Java update, right? I can't see any other issues with maintaining two versions.
  6. What about 86 bit java?

    Exia likes this.
  7. The typical issue is setting the default JRE and/or running with an alternative.

Share This Page