Congrats on the release! I think the fact that many of the highlights of recent Gleam releases are focused on “Developer Experience” improvements is a testament to the strong design of the language itself, and the community’s focus on making it a pleasant experience to work with.
Minor irritant for me… at every new Gleam version announcement, I visit the home page, see the sample code block for task.async, yearn for more info on that, then search for “task” in both the standard library and packages index, to no avail. I wish someone would take the time to address that glaring omission.
Being able to search by module in the package index is a great idea! Would you mind opening an issue for that, along with any other UX improvements you can think of? Thank you
I feel like gleam has everything I need to write soft-real-time web applications. I’m really impressed.
The only thing missing for me at this point is git dependencies. I think this is still on the roadmap, but I only see “private packages” here. Anyone know if git dependencies are planned?
Is it possible to learn Gleam for the front end without really knowing about the browser/front end ecosystem otherwise? My use case is putting an interactive overlay on top of an interactive iframe.
I’m not totally sure I’m understanding your question correctly, but I don’t personally believe it’s possible to program successfully in any technical domain without learning something about the domain.
Learning Gleam for frontend would be learning regular frontend, the same as in any other language.
I phrased it quite poorly. I guess I’m asking whether it presents a non-leaky abstraction/framework for web front ends (so you don’t have to read discussions of how to manipulate the dom in JS). The answer is: probably yes. Lustre looks interesting.
Ah you probably don’t need to know how to manipulate DOM with any framework these days, in JavaScript or any other language. Those APIs tend to be avoided in avoid of declarative ones.
Yeah I was a fan of CoffeeScript back in the day, and I spent some time trying Elm but that was not it. It’d be nice if so much modern infrastructure wasn’t based off a language “written in 10 days”.
Congrats on the release! I think the fact that many of the highlights of recent Gleam releases are focused on “Developer Experience” improvements is a testament to the strong design of the language itself, and the community’s focus on making it a pleasant experience to work with.
Thank you!
I’ve been dipping in a bit and I’m finding tiny projects without documentation and tests which is definitely not my idea of “developer experience”.
Minor irritant for me… at every new Gleam version announcement, I visit the home page, see the sample code block for task.async, yearn for more info on that, then search for “task” in both the standard library and packages index, to no avail. I wish someone would take the time to address that glaring omission.
Being able to search by module in the package index is a great idea! Would you mind opening an issue for that, along with any other UX improvements you can think of? Thank you
Done. https://github.com/gleam-lang/packages/issues/46 .
Your comment on my submitted issue led me to https://gloogle.run/ and … nice!
Adding a link to this in the Packages page might be the simplest solution, would it not,?
It looks like that needs to be updated to require
gleam/otp/taskNor is gleam/otp listed in the std lib docs.
gleam/otpcomes fromgleam_otp, a separate package.Ok now I see. Packages search does not include namespace entries results, making task unreachable.
Both a minor irritant and a glaring omission? ;-)
Yep. A glaring omission can still be seen as small stuff. I’m not sweating it. :)
I feel like gleam has everything I need to write soft-real-time web applications. I’m really impressed.
The only thing missing for me at this point is git dependencies. I think this is still on the roadmap, but I only see “private packages” here. Anyone know if git dependencies are planned?
Great work gleam team!
This is currently being worked on by the core team!
Great news, thanks!
Is it possible to learn Gleam for the front end without really knowing about the browser/front end ecosystem otherwise? My use case is putting an interactive overlay on top of an interactive iframe.
Elm is, or at least can be, pretty good at insulating you from the wild and crazy world of JS. I’ve had pretty good luck with it.
Anybody looking into Elm should also look into the Lobster users that regretted it. I am very happy with PureScript.
I’m not totally sure I’m understanding your question correctly, but I don’t personally believe it’s possible to program successfully in any technical domain without learning something about the domain.
Learning Gleam for frontend would be learning regular frontend, the same as in any other language.
I phrased it quite poorly. I guess I’m asking whether it presents a non-leaky abstraction/framework for web front ends (so you don’t have to read discussions of how to manipulate the dom in JS). The answer is: probably yes. Lustre looks interesting.
Ah you probably don’t need to know how to manipulate DOM with any framework these days, in JavaScript or any other language. Those APIs tend to be avoided in avoid of declarative ones.
Don’t know about that use case specifically but check out Lustre
How realistic is using Gleam as an alternative to TypeScript today?
It’ll come down to personal taste and your specific requirements really. Folks are happily using Gleam for frontend and commercial programming.
This is what I’m looking for: a language that compiles to javascript that’s usable and not this monstrosity that TS is these days
Yeah I was a fan of CoffeeScript back in the day, and I spent some time trying Elm but that was not it. It’d be nice if so much modern infrastructure wasn’t based off a language “written in 10 days”.
I used to use node and typescript for pet projects. I’m using Gleam for the last two I started and so far it suits all my needs.
great job with gleam
Thank you!