lpil

No no, you misunderstand. It doesn't mean the same thing as you imply with your previous comment.

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.

Because that means something else.

> Black and White lives matter, but that's not what Glean is signalling.

It is! citation: I wrote it.

We should really remove the cheatsheets, they have not been maintained in many years.

What were the inaccuracies? I'm not aware of any, but we can fix any that are found right away.

Hi, I'm the lead maintainer of Gleam.

> 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.

Hello! I'm the maintainer of Gleam. We are not rewriting OTP, regular OTP is used in Gleam. Most commonly the typed Gleam APIs for OTP are used, but you can use the untyped Erlang APIs if you wish.

This is the same as in Elixir, where macro-enabled APIs are offered, and they just wrap the regular Erlang APIs.

It only happens on hacker news. Elsewhere it is not mentioned or it is praised.

Gleam does have a formal code of conduct.

Gleam is the same as SQLite, we have some community values on the website but the licence doesn’t exclude anyone from using the software.

How you behave in community spaces is 100% related to the project.

I agree, that would be very silly. I don't think you can compare not tolerating racists to mandating a particular car colour.

Sorry, I've been unclear.

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.

All open source projects have a political agenda. That's the purpose of the licence, to force certain behaviour.

In a world with package management there’s no practical difference between the core modules being in one package or multiple packages.

All open source projects are political by their very nature.

This is the same as Elixir, you need to specify what Erlang function to use in that language if you want to use Erlang code. The only difference is that Gleam has a more verbose syntax for it.

You can use all the BEAM debuggers and tracing tools, and Gleam has a print debugging keyword.

Unfortunately there is not yet a plugin for the BEAM debuggers for them to use Gleam syntax.

SQLite is likely the most widely used production database due to its widespread usage in desktop and mobile software, and SQLite databases being a Library of Congress "sustainable format".

I presume they checked out Gleam years ago, or their investigation was more shallow.

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.

We've not had any proposals for a design like that. We are open to proposals though! I wrote a blog post detailing the process here: https://lpil.uk/blog/how-to-add-metaprogramming-to-gleam/

OCaml's modules are not implicitly instantiated, so they provide the same DX and APIs as you would get in Gleam.

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.

Thank you!

Free software was started as a political movement by Stallman et al. Why would we stop now?

There’s several options, depending on what you want. The most commonly used option is the language server.

Yes, one would use higher order functions, as is common in Erlang, Elixir, OCaml, Elm, etc.

I would be very interested in hearing about your experience writing Gleam and the problems you have!

We regularly collect feedback and haven’t got problems reported here, so your feedback saying otherwise would be a useful data point.

Totally. This is where I would generate them.

In Gleam code generators are most commonly used, similar to in C#, Go, or Elm.

Ah, that’s good feedback. I agree, that documentation is misleading. I’ll fix them ASAP.

> Elixir also provides for much OTP functionality via direct access to the Erlang libraries.

This is the norm in Gleam too! Gleam’s primary design constraint is interop with Erlang code, so using these libraries is straightforward and commonplace.

In Gleam we would typically write this code with `use`, which doesn’t introduce nesting.

OTP is a very complex subject and quite unusual in its scope, and it’s not even overly clear what it even is. Even in Erlang and Elixir it’s commonly confused, so I think it’s understandable that Gleam has the same problem further still with its more distinct programming style.