I half-remember read something or watching a livestream by lpil where he discussed the process of designing Gleam. Are there any language features that Louis thinks are cool/useful/interesting but will never make it into Gleam b/c they go against the design principles of Gleam? The intentional lack of a feature is an important design decision in itself.
#Language Features that will never be in Gleam
next oyster
vagrant hearth
ad-hoc polymorphism is one, I believe
hayleigh was talking about it just today, I believe
next oyster
my head cannon is that Gleam is the FP version of Golang in spirit in some ways
I imagine dependent types are a big NO as well
winter roost
My guess is first-class mutation (there is ETS etc)
vagrant hearth
my head cannon is that Gleam is the FP version of Golang in spirit in some ways
i was thinking about this a few days ago too
zenith crag
Object orientation is a big one
I think there's a lot of really interesting and practical stuff there, but it's just not a good fit
winter roost
Of we go to great gloop 😄 (user land library based on ETS :D) 💀