lpil

11 ms·

121.
by lpil 2y ago
> Maybe one of the next BEAM languages will handle that automatically for us. It not being automatic is a feature as that pattern is only what you want in the trivial case, but in real programs you are going to want more control. In earl
122.
by lpil 2y ago
I believe this is on the roadmap for the Lustre framework.
123.
by lpil 2y ago
It's not an afterthought at all, but due to Gleam being a new language we do not have much documentation for the actor framework, so you are largely expected to be familiar with Erlang's implementation. The community voted that th
124.
by lpil 2y ago
> There's a fair amount similar but things like message passing are implemented as a library in gleam [0] rather than being a part of the core language, so you might say the big things that make erlang _erlang_ are not part of Gleam
125.
by lpil 2y ago
Thanks for sharing!
126.
by lpil 2y ago
OTP will never be 100% supported, it's an application framework for a dynamically typed language and as such much of it doesn't make sense in a statically typed language.
127.
Gleam v1.1.0(gleam.run)
8 points by lpil 2y ago|0 comments
128.
by lpil 3y ago
Correct, it’s not.
129.
by lpil 3y ago
Unlike in Haskell `{}` are not optional in Gleam, so that would be written like so: use a <- one({ use b <- two // etc })
130.
by lpil 3y ago
> it's more confusing (and less expressive) than full-on do-notation (or F#-like "computation expressions"). It's strictly more expressive than do-notation. Anything that Haskell's `do` can do Gleam's `use`
131.
Gleam v1.0.0 Released(gleam.run)
74 points by lpil 3y ago|4 comments
132.
by lpil 3y ago
Exciting times!
133.
by lpil 3y ago
Gleam can be used from the Erlang REPL easily, there's no additional runtime/overhead or complex translation between the two languages.
134.
by lpil 3y ago
I would definitely bet my start up on Gleam!
135.
by lpil 3y ago
I prefer the simplicity of Erlang, Elixir is a much larger language and has some quirks.
136.
by lpil 3y ago
You actually said that Gleam won't reach Elixir's levels of success.
137.
by lpil 3y ago
Best not confuse your personal preference for macros with a requirement for the global programming population. Most languages do not use macros, metaprogramming is comparatively niche and doesn’t lend itself well to the style of programming
138.
by lpil 3y ago
We're interested in some form of metaprogramming or code generation in future, but we do not yet have a design yet that we're happy enough with to make the official one. It's important to us to keep the language easy to under
139.
by lpil 3y ago
Thank you, I'll fix that link now.
140.
by lpil 3y ago
Gleam started in 2018 but has only been worked on full time for 1 year. Compared to Elixir it's very young. I think it's a bit strange to bring up macros here. There are lots of languages that don't have Elixir's macro s
141.
by lpil 3y ago
There is a blog post with a description of how it is implemented here: https://gleam.run/news/gleams-new-interactive-language-tour/
142.
Gleam's New Interactive Language Tour(gleam.run)
4 points by lpil 3y ago|0 comments
143.
Gleam v0.34(gleam.run)
4 points by lpil 3y ago|0 comments
144.
A Gleamy Exploration(trulyao.dev)
1 points by lpil 3y ago|0 comments
145.
Gleam Language, Types for the Beam(semaphoreci.com)
2 points by lpil 3y ago|0 comments
146.
Gleam v0.33 Released(gleam.run)
8 points by lpil 3y ago|0 comments
147.
by lpil 3y ago
Hi there, I'm the maintainer of the Gleam website. > The trans rights are human rights slogan is typically used as a euphemism for removing all single-sex spaces and services To be clear, the Gleam community does not support the ban
148.
by lpil 3y ago
Golang had a very similar statement on their homepage when the Gleam homepage was created. It's very normal.
149.
by lpil 3y ago
That's not at all what trans rights are.
150.
by lpil 3y ago
Mocks are deliberately not supported by Gleeunit as I (the maintainer) believe they are strictly worse than using dependency injection, and often result in dramatically lower quality code.

More ›