Looks really interesting. I‘ve always admired the erlang community but writing slang always felt like something was missing and having recently dove into Haskell this looks like it has a lot of potential.<p>Few questions:
1) how stable is hamler? I’m eager to dive in but know I don’t have time to work through frequent language bugs if I’m going to do anything real with it.<p>2) A good reference, which I didn’t see in the doc and having a hard time articulating my self would be a comparison of Hamler vs Haskell erlang FFI support? <a href="https://hackage.haskell.org/package/erlang" rel="nofollow">https://hackage.haskell.org/package/erlang</a><p>3) What are the key differences between Hamler And Haskell (sort of a continuation of the last question)?
Added to my Erlang resources gist. Amazing how many languages are now available for the BEAM.<p><a href="https://gist.github.com/macintux/6349828#alternative-languages-targeting-the-erlang-vm" rel="nofollow">https://gist.github.com/macintux/6349828#alternative-languag...</a>
I'm relatively ignorant about this, but a common refrain I've heard repeated about strongly typed languages targeting the BEAM is that typing of messages is [hard / an ongoing research problem / impossible]. Can anyone comment on whether that is true and what that says about this language?
This would be interesting to check out, but in my experience with using Erlang for a IIoT type application, gradual typing with dialyzer is sufficient for large code bases. We also employed property-based testing to a limited degree.<p>The complicated part of applications that Erlang is well suited for is reasoning about the state of the entire application based on the state of the various concurrent processes. Perhaps I'm missing something, but I don't think that's something that stronger type systems can really help more than what you would get from other tools like concolic testing, TLA models, etc.
Interesting to see this kind of work coming out of China.<p>> The founding team of EMQ hails from Huawei, IBM, Amazon, and Apple with years of experience and a deep understanding of the industry.<p><a href="https://www.emqx.io/about" rel="nofollow">https://www.emqx.io/about</a>
Another options for typed actors is Akka for Scala and Java: <a href="https://doc.akka.io/docs/akka/current/typed/actors.html" rel="nofollow">https://doc.akka.io/docs/akka/current/typed/actors.html</a>
Looks cool! Is this meant for use in embedded applications? I couldn’t find info about compile targets and performance on resource constrained systems (in other words, can I target an Arduino?)
How does it compare to PureScript used with purerl? <a href="https://github.com/purerl/purerl" rel="nofollow">https://github.com/purerl/purerl</a>
Has anyone tried writing a distributed app with Hamler ? It would be great to see an example that shows off the inbuilt messaging of erlang and the static typing of Haskell.
This looks cool! The BEAM absolutely needs languages on it with a solid functional type system.<p>Curious to see what interacting with the OTP with its callbacks actually looks like.
A new family member! It's good to see BEAM is getting traction.<p>The documentation seem to be work in progress. I wonder how to type processes/genservers. But generally, it seems to be a good fit, since most Erlang code is already pretty functional (immutable, no variables, etc).