1. 20
  1.  

  2. 2

    I think Pony a bit more cumbersome to use than many other languages, at least for a simple “Hello, World!” example in SDL2, but it feels surprisingly solid. https://github.com/xyproto/sdl2-examples/blob/master/pony/main.pony

    1. 4

      I will say, this is pony program that uses SDL by directly linking against external c functions! Most SDL hello world examples you’ll see in other languages use a library wrapping the external calls. I think it speaks volumes that in fact the Pony source is both readable and short, especially considering that Pony is a managed language, with support for actors. (In comparison, the C FFI in both Go and Erlang tends to be much harder)

      1. 1

        It uses SDL2 directly only because no SDL2 library were available for Pony at the time (I’m not sure if there is one available now).

      2. 3

        I just did some exercises in Pony and Rust and I definitely found Pony the more elegant and easy language; but with much worse library support

        1. 4

          We definitely have a considerably smaller community than Rust at this point. In part, I think that is:

          1- Rust has corporate backing and people paid to work on it 2- It’s post 1.0 and most people won’t consider using pre-1.0 stuff

          More people contributing to the Pony ecosystem (including libraries) is something we could really use and would happily support as best we can. We’ve had a lot of excited people start to pitch in. Most haven’t contributed to open source projects before and I think for many, the shine rather quickly rubs off. I don’t blame them, maintaining open source software is… well, it’s an “interesting hobby”.

          1. 1

            Absolutely agree. Even contributing to a few projects, I can see that I wouldn’t want to be a maintainer without being paid or “it” being my big idea.

            I don’t do much system level programming, so I don’t need either, really, so I’m very unlikely to step up.

            A bridge to rust might help though?

            1. 5

              A bridge to rust might help though?

              Pony can directly call into C (and therefore into Rust) and generate C headers, which Rust can consume to generate interfaces. The biggest problem for “just” using both from both sides is language semantics outside of the function call interface that the C ABI provides. Also, Rusts ABI is currently private.

              I don’t do much system level programming, so I don’t need either, really, so I’m very unlikely to step up.

              Both Rust and Pony provide safety guarantees and features way past “safe systems programming” and Rust is definitely used as a “wicked fast Python” in some circles. It’s an interesting space to work in, currently :).

        2. 2

          I really like the syntax, and the underlying ideas. I recently speed read through the tutorial, and the most daunting aspect of it (for me) was the reference capabilities part. I hope I can find a side project to play with it some more.

          Plus the language is named pony, which makes it instantly great. ;)

        3. 1

          I think I found a way to install Visual Studio Build Tools that doesnt require a 600 MB - 60 GB download:

          https://cup.github.io/autumn/extras/vs-build-tools

          I am working on turning it into a Python script - if it works it would close:

          https://github.com/ponylang/ponyc/issues/2079

          as far as Im concerned anyway.