1,089 karma · joined March 17, 2016
If anyone would like to give me a large amount of money in exchange for my publishing a mirror on your git forge, please get in touch ;)
Writing is contextual, if one only looks at the literal then one misses the other half of the meaning. Unfortunately your proposed change has added context that undermine your honourable and well-intentioned message.
It is! citation: I wrote it.
> I don't know the current state of Gleam OTP, but last I checked it wasn't great.
Gleam uses regular OTP, it doesn't have a distinct OTP framework separate from other BEAM languages.
This is the same as in Elixir, where macro-enabled APIs are offered, and they just wrap the regular Erlang APIs.
Gleam does have a formal code of conduct.
I agree, that would be very silly. I don't think you can compare not tolerating racists to mandating a particular car colour.
The runtime behaviour and cost of calling an Erlang function is the same in Elixir and Gleam, however the syntax is more verbose in Gleam as it asks for type information, while in Elixir this is optional.
Unfortunately there is not yet a plugin for the BEAM debuggers for them to use Gleam syntax.
That aside, it is normal in Elixir to use Erlang OTP directly. Neither Elixir nor Gleam provides an entirely alternative API for OTP. It is a strength that BEAM languages call each other, not a weakness.
Elixir does have protocols, but they are extremely limited compared to type classes, traits, etc, and they're uncommonly used compared to writing concrete code.
We regularly collect feedback and haven’t got problems reported here, so your feedback saying otherwise would be a useful data point.