• interpreted languages are inherently slower than native code. Because huawei controls the hardware they don’t need portability and can focus on speed

      on a phone, using java will give all the disadvantages with no advantages

      look at iphone vs android, for years apple had better battery life and better performance even with half the ram, a worse cpu and smaller batteries

      • Java isn’t an interpreted language any more than C. Java gets compiled into its own machine code developed by Sun. That machine code can be converted to native code or just run “interpreted.” (which is more like emulation.)

        Maybe you should learn more about something before you criticize it.

        • I can’t think to any program made in java that isn’t a memory hog.

          Look at the performance of Minecraft java vs native

          Or vuze that uses 20x the memory of qbittorrent for doing the same stuff but with less features

          So either java devs don’t know how to optimize code, or the language itself has some problems

          • Of course there comes the Minecraft comparison. Which also conveniently ignores the fact that Minecraft can run incredibly fast using certain performance mods. It’s not Java, it’s just shitty programming / code that hogs its performance.

            •  taanegl   ( @taanegl@beehaw.org ) 
              link
              fedilink
              English
              111 months ago

              Pretty much large suathes of banking and financing companies, as well as other massive industries, which btw are hiring and pay well.

              Java (or rather JVM) is slow at first, but once a JVM has “booted” Java performance wise is on par with the performance of other languages, even system languages. This isn’t too apparent in the open source world, because Oracle.

              Most infrastructure running on Java have been doing so for decades and continues to be implemented, not because the project managers are idiots, but because the software is portable and java (believe it or not) is getting better, similar to how JS has gotten better post-TypeScript.

              So let’s not throw the language and infrastructure on the fire in a time when we know *technical debt" is just an executive excuse to allow rushed, faulty and unoptimized programming in order to meet insane deadlines by white collar deadites.

              “Agile”, “crunch”, “technical debt”. We’ve been taken for absolute fools, and now we’re blaming the tools. Smh.

      • The language has nothing to do with what you describe in your last paragraph. There are a lot of reasons what that was happening, and using Java is not one of them. Just the openess of the OS and how it was written was enough to justify such a difference vs a closed OS with a fraction of the possibilities

        Also Android is not using just Java, otherwise you would be able to run any normal Java app without “hacks”