Replies: 6 comments 6 replies
-
A rewrite of Massa in Go? |
Beta Was this translation helpful? Give feedback.
-
Hi Marcel, thanks for your reply. I see you've spent some time thinking about this and that's very good. Anyway I just wanted to open up to more thoughts. Note: I'm not a type-addicted developer and I don't think this would be a reason to adopt a proxy language or not, as I've spent time with languages that use both static and dynamic typing and have gotten used to both styles. But I tend to agree with Matz, creator of Ruby, that we should stop writing programs using machine languages and use languages with more natural characteristics, therefore, expressing like I consider an excess of zeal with the cpu, despite knowing that the possibility of using explicit types will help in debugging problems. I can finally sleep peacefully with types or without types. |
Beta Was this translation helpful? Give feedback.
-
Opening a new parenthesis that might not fit in this discussion, I think we can try a mixed approach with Elixir and Gleam, so we can easily add types to the project. We can keep all the OTP part of the project like Applications, GenServers, and Supervisors in Elixir and use Gleam to define the service modules. |
Beta Was this translation helpful? Give feedback.
-
@wesleimp I would love to hear your ideas too |
Beta Was this translation helpful? Give feedback.
-
A point I touched on briefly would be about the ability to schedule different proxies to run on the same cluster, in this sense we could use k8s tenants and labels to deploy a version of the proxy written in Go on Edge Nodes (suddenly the client uses something like kube-edge), and also schedule workloads with the proxy using Lunatic (rust) on this same cluster on Wasi Nodes (with krustlet), or even running the browser with something like Lumen and those Nodes running specific proxies could live with the default proxy written in Elixir on conventional Nodes. |
Beta Was this translation helpful? Give feedback.
-
Interesting discussions and thoughts. I haven't spent time on this topic. But I think it would be better to stick with the Erlang Ecosystem. It is nice to try to mix it with Go and Rust and I am not sure we have the capacities to deal with that now. This is my humble opinion on this. |
Beta Was this translation helpful? Give feedback.
-
https://github.com/ergo-services/ergo
Beta Was this translation helpful? Give feedback.
All reactions