• @[email protected]
      link
      fedilink
      1424 days ago

      Also the difference between TS and JS doesn’t make sense at first glance. 🤷‍♂️ I guess I need to read the research.

      • @[email protected]
        link
        fedilink
        624 days ago

        My first thought is perhaps the TS is not targeting ESNext so they’re getting hit with polyfills or something

      • @[email protected]
        link
        fedilink
        English
        4
        edit-2
        24 days ago

        It does, the “compiler” adds a bunch of extra garbage for extra safety that really does have an impact.

        • @[email protected]
          link
          fedilink
          124 days ago

          Only if you choose a lower language level as the target. Given these results I suspect the researchers had it output JS for something like ES5, meaning a bunch of polyfills for old browsers that they didn’t include in the JS-native implementation…

        • @[email protected]
          link
          fedilink
          424 days ago

          I thought the idea of TS is that it strongly types everything so that the JS interpreter doesn’t waste all of its time trying to figure out the best way to store a variable in RAM.

          • @[email protected]
            link
            fedilink
            824 days ago

            TS is compiled to JS, so the JS interpreter isn’t privy to the type information. TS is basically a robust static analysis tool

          • @[email protected]
            link
            fedilink
            524 days ago

            The code is ultimately ran in a JS interpreter. AFAIK TS transpiles into JS, there’s no TS specific interpreter. But such a huge difference is unexpected to me.

            • @[email protected]
              link
              fedilink
              English
              324 days ago

              Its really not, have you noticed how an enum is transpiled? you end up with a function… a lot of other things follow the same pattern.

              • @[email protected]
                link
                fedilink
                123 days ago

                No they don’t. Enums are actually unique in being the only Typescript feature that requires code gen, and they consider that to have been a mistake.

                In any case that’s not the cause of the difference here.

                • @[email protected]
                  link
                  fedilink
                  English
                  122 days ago

                  This isn’t true, there are other features that “emit code”, that includes: namespaces, decorators and some cases even async / await (when targeting ES5 or ES6).

                  • @[email protected]
                    link
                    fedilink
                    122 days ago

                    Ah yeah I forgot about namespaces. I don’t think they’re a popular feature.

                    The other two only generate code for backwards compatibility. When targeting the latest JavaScript versions they don’t generate anything.

                    Ok decorators are technically still only a proposal so they’re slightly jumping the gun there, but the point remains.

        • @[email protected]
          link
          fedilink
          424 days ago

          In theory Java is very similar to C#, an IL based JIT runtime with a GC, of course. So where is the difference coming from between the two? How is it better than pascal, a complied language? These are the questions I’m wondering about.

        • @[email protected]
          link
          fedilink
          English
          424 days ago

          Because usually they use the super fat flavor of Java. Jabba Fatt tier of lardiness Java.

          • @[email protected]
            link
            fedilink
            English
            6
            edit-2
            24 days ago

            I’m using the fattest of java (Kotlin) on the fattest of frameworks (Spring boot) and it is still decently fast on a 5 year old raspberry pi. I can hit precise 50 μs timings with it.

            Imagine doing it in fat python (as opposed to micropython) instead like all the hip kids.

        • esa
          link
          fedilink
          324 days ago

          And it powers a lot of phones. People generally don’t like it when their phone needs to charge all the freaking time.

          • @[email protected]
            link
            fedilink
            English
            3
            edit-2
            24 days ago

            I ran Linux with KDE on my phone for a while and it for sure needed EVEN MORE charging all the time even though most of the system is C, with a sprinkle of C++ and QT.

            But that is probably due to other inefficiencies and lack of optimization (which is fine, make it work first, optimize later)

            • esa
              link
              fedilink
              424 days ago

              Yeah, and Android has had some 16 years of “optimize later”. I have some very very limited experience with writing mobile apps and while I found it to be a PITA, there is clearly a lot of thought given to how to not eat all the battery and die in the ecosystem there. I would expect that kind of work to also be done at the JVM level.

              If Windows Mobile had succeeded, C# likely would’ve been lower as well, just because there’d be more incentive to make a battery charge last longer.

              • @[email protected]
                link
                fedilink
                224 days ago

                C# has been very optimized since .NET Core (now .NET). Also jit compiler and everything around it.

        • @[email protected]
          link
          fedilink
          English
          224 days ago

          etalon
          /ˈɛtəlɒn/
          noun Physics
          noun: etalon; plural noun: etalons

          a device consisting of two reflecting glass plates, employed for measuring small differences in the wavelength of light using the interference it produces.

          I don’t see how that word makes sense in that phrase

        • @[email protected]
          link
          fedilink
          124 days ago

          That definitely raised an eyebrow for me. Admittedly I haven’t looked in a while but I thought I remembered perl being much more performant than ruby and python

    • @[email protected]
      link
      fedilink
      English
      524 days ago

      WASM would be interesting as well, because lots of stuff can be compiled to it to run on the web

      • Ben Matthews
        link
        fedilink
        2
        edit-2
        24 days ago

        Indeed, here’s an example - my climate-system model web-app, written in scala running (mainly) in wasm
        (note: that was compiled with scala-js 1.17, they say latest 1.19 does wasm faster, I didn’t yet compare).
        [ Edit: note wasm variant only works with most recent browsers, maybe with experimental options set - if not try without ?wasm ]

          • Ben Matthews
            link
            fedilink
            English
            224 days ago

            Oh, it’s designed for a big desktop screen, although it just happens to work on mobile devices too - their compute power is enough, but to understand the interactions of complex systems, we need space.

    • I Cast Fist
      link
      fedilink
      424 days ago

      Looking at the Energy/Time ratios (lower is better) on page 15 is also interesting, it gives an idea of how “power hungry per CPU cycle” each language might be. Python’s very high

    • JustEnoughDucks
      link
      fedilink
      524 days ago

      I would be interested in how things like MATLAB and octave compare to R and python. But I guess it doesn’t matter as much because the relative time of those being run in a data analysis or research context is probably relatively low compared to production code.

      • esa
        link
        fedilink
        724 days ago

        Is there a lot of computation-intensive code being written in pure Python? My impression was that the numpy/pandas/polars etc kind of stuff was powered by languages like fortran, rust and c++.

    • @[email protected]
      link
      fedilink
      English
      724 days ago

      I guess we can take the overhead of rust considering all the advantages. Go however… can’t even.

    • @[email protected]
      link
      fedilink
      123 days ago

      For Haskell to land that low on the list tells me they either couldn’t find a good Haskell programmer and/or weren’t using GHC.

    • @[email protected]
      link
      fedilink
      6
      edit-2
      24 days ago

      For Lua I think it’s just for the interpreted version, I’ve heard that LuaJIT is amazingly fast (comparable to C++ code), and that’s what for example Löve (game engine) uses, and probably many other projects as well.

    • Caveman
      link
      fedilink
      123 days ago

      Wonder what they used for the JS state since it’s dependent on the runtime.

    • @[email protected]
      link
      fedilink
      324 days ago

      Every time I get surprised by the efficiency of Lisp! I guess they mean Common Lisp there, not Clojure or any modern dialect.

      • @[email protected]
        link
        fedilink
        123 days ago

        Yeah every time I see this chart I think “unless it’s performance critical, realtime, or embedded, why would I use anything else?” It’s very flexible, a joy to use, amazing interactive shell(s). Paren navigation is awesome. The build/tooling is not the best, but it is manageable.

        That said, OCaml is nice too.