3 ms·
You should give Gleam a shot. No REPL, but its simplicity, functional-ity and the BEAM lend themselves to the get-shit-done approach
by oDot 2y ago
You should give Gleam a shot. No REPL, but its simplicity, functional-ity and the BEAM lend themselves to the get-shit-done approach
- ilrwbwrkhv 2y agoGleam takes more code to write than rust. Doesn't have a strong enough documentation / ecosystem yet. But I agree the beam VM is very underutilized and underappreciated.
- MarkMarine 2y agoI see gleam as a sweet spot, the type system I’d prefer to be writing (rust’s sensible one) and I never have to fight with the borrow checker
- tasuki 2y ago> Gleam takes more code to write than rust. Do you have some source for that? Perhaps an example?
- ilrwbwrkhv 2y agoNo. Take that with a grain of salt. I did some large file reading in the past and gleam doesn't have a good abstraction for that yet whereas in rust it was straightforward. Simplifile basically reads the whole file into memory.
- cess11 2y agoThey've added https://hexdocs.pm/file_streams/0.6.0/ https://hexdocs.pm/file_streams/0.6.0/ for this purpose. There's a bit of ceremony but similar to how you can interface with Java libraries from Clojure you can pull in Erlang when Gleam isn't enough. You can do some code shortening with use, https://erikarow.land/notes/using-use-gleam https://erikarow.land/notes/using-use-gleam, but it will likely always be rather chatty and won't support metaprogramming: https://lpil.uk/blog/how-to-add-metaprogramming-to-gleam/ https://lpil.uk/blog/how-to-add-metaprogramming-to-gleam/
- ndr 2y agoImmutable data and REPL is where is at for iteration speed though.