Gleam, specifically with Lustre makes me excited about frontend in a way that I haven’t been before. I missed out on Elm when it was at its peak, and Gleam’s focus on good tooling is really encouraging for its future :)
Also, it seems like you’ve a word in this paragraph:
If you place your cursor on the type header and select the code action in your, then it’ll be updated to this:
Coming from Rust with serde and #[derive(Desieralize)] I’ve definitely found decoders a bit of a chore, so I’m quite pleased to see that new generate decoder action.
Edit:
To avoid this packages place their modules within their own namespace. For example, if I am writing a package named pumpkin I would place my modules within the src/pumpkin/ directory.
Sometimes people from other ecosystems with per-package isolation may not understand this convention and place all their code in the top-level namespace
Your package structure looks fine to me (your only Gleam file matches the name of the package), although I’d probably recommend renaming your ffi file to bytesize_ffi.mjs as this appears to be the convention.
Gleam, specifically with Lustre makes me excited about frontend in a way that I haven’t been before. I missed out on Elm when it was at its peak, and Gleam’s focus on good tooling is really encouraging for its future :)
Also, it seems like you’ve a word in this paragraph:
Are there any companies/known projects running on Gleam?
The eyg structural editor is built with Gleam/Lustre.
Also, it looks like SteerLab is using Gleam in its stack and hiring devs interested in it:
There are probably others that I don’t know of.
Good to know, thank you!
I’m hoping to get some case studies published in the next year or so.
Coming from Rust with serde and
#[derive(Desieralize)]I’ve definitely found decoders a bit of a chore, so I’m quite pleased to see that new generate decoder action.Edit:
It’s me, I’m people from other ecosystems with per-package isolation. Does this mean I should have an extra layer of hierarchy in my package: https://github.com/wezm/gleam_bytesize/tree/main/src ?
Your package structure looks fine to me (your only Gleam file matches the name of the package), although I’d probably recommend renaming your ffi file to
bytesize_ffi.mjsas this appears to be the convention.You’re good!
Whew, good to know.
Git is required to have a repository? Is Git the only supported VCS? No VCS-independent tarballs?
Git isn’t required but
gleam newcan initialise a git repository if you would like to use git.