Come join us on ANY mastodon server (https://t.co/IxP86vRS9h), then once you've created an account, search for us (and follow!): @[email protected]
Web address: https://t.co/IFNyYxkyZT
Check out this fireside chat with @rvirding & @oubiwann at #CodeBEAM V America 2021, for a discussion on practical considerations when creating applications and services in OTP on the BEAM.
Watch the video and find out more at:
https://t.co/MaLsRUWj4W
@adolfont@frescosecco Most folks seem to use the #beam dev tool #rebar3 ... and with that, LFE is just another dep, like any other Erlang/BEAM library (or app)
@MiguelCoba_ @frescosecco Fun fact: Robert created LFE around the same time that Clojure was coming into existence, and it was years later before he ever heard of Clojure :-D
(it's actually largely based on MacLisp / ZetaLisp and Scheme ...)
@mayureshkathe@rvirding In the functional view, exceptions are a terrible abstraction. Practically, they're even worse. The world's just gotten used to them. Handling errors the "Erlang/OTP way" will bring new life and _relief_ to your code :-D Try it!
@mayureshkathe@ErlangLisp I think the main thing to realise that LFE runs in the Erlang/OTP environment and is an integral part of that environment. This means that detecting and handling conditions needs to be done the OTP way, and OTP has what you need to work with "exceptions" as we call them