davydog187
davydog187 on Hacker News
We use Elixir at TV Labs to build our web services, a realtime matching engine, execute sandboxed Lua code, talk to microcontrollers over binary protocols, machine learning, and much more.
It is an excellent general purpose language that succeeds in a lot of domains.
Check out my conversation from Developer Voices for more info
https://youtu.be/_MwXbHADT-A?si=2lRqjwAY9dsODyhW
Touche, although that is a 5 line utility.
Filtering which search results? On hex.pm that’s irrelevant. On good “library name + elixir”
Early in the Elixir days, every library was named Thing-ex of ex-Thing.
IMO this is really lazy in terms of naming and from a usage perspective, you get really tired of typing that out in code.
I think we can do better
I have a personal mission to never name any libraries with the -ex prefix
Probably not, you should come to Code BEAM NYC, although a bit of a trek for you.
I will be trying to travel more in 2026
Elixir is not a sandboxed language, so you can't just accept arbitrary Elixir programs from users and execute them inside of your application without security concerns. Lua, on the other hand, can be executed in a sandboxed fashion, limiting and constraining the reach of user programs.
Check out Anthony Accomazzo's post about Mini-Elixir, which does a great job breaking this down much further https://blog.sequinstream.com/why-we-built-mini-elixir/
There is a fennel channel in the discord/slack if you're interested. I'm not sure how successful it has been
Both the Lua library and Luerl predate Pythonx. I started this library nearly 2 years ago, its only now that I'm releasing a stable version.
However, Pythonx was originally created by a member of our team, Cocoa, who built it in her own free time. The Livebook team forked her project, conceptually, and released it.
https://github.com/cocoa-xu/pythonx
Thanks, I really appreciate that. While its not my main focus by any means, its been a really fun project to chip away at (both the higher level library and Luerl itself).
I do think that it has the potential to be really great with continued investment
Let me know if you have any questions, I'd be happy to assist
Thanks Josh, hope to see you soon, its been a while
Author here!
Luerl++ is not a valid module name :)
More seriously, I considered alternate names, but settled on this because it was short, literal, and given that its in the context of Elixir, makes sense when using it.
As you stated, the hope is to consolidate it into Luerl at some point
Posted by
davydog187 on Tuesday May 13, 2025 @09:03AM
from the davelucia.com dept.
For most of the workloads you’re putting on the BEAM, they are IO bound and this is not of any consequence
Ok but in literally any other language you minimally need this setup to do PubSub.
Elixir gives more options and lets you do it natively.
Also, there are simpler options for clustering out there like https://github.com/phoenixframework/dns_cluster (Disclaimer: I am a contributor)
Yay, I have a commit or two in this release! So excited to see the type system continue to roll out
Whoops, thought you were OP
Rather than promtail, have you looked at Vector? I just started an MVP of shipping logs directly to our product for end-user consumption using Vector + NATS, and it’s a killer combination.
Compared to Promtail, you have incredibly flexibility with how you collect, transform, and ship logs, with end to end confirmation and great documentation. Using promtail felt inferior once I made the switch
https://vector.dev/
https://docs.nats.io/
Posted by
davydog187 on Friday October 25, 2024 @10:55AM
from the massdriver.cloud dept.
Posted by
davydog187 on Thursday July 04, 2024 @01:52PM
from the twitter.com dept.
Both the Elixir and Gleam type systems run at compile time (and whenever you recompile during development)
There are no plans for runtime checking AFAIK
We're pretty close to the same conclusion. We can't run a business on an unstable platform.
Posted by
davydog187 on Monday April 01, 2024 @03:17PM
from the twitter.com dept.
I think you need to go deeper, because it does exactly all the things you’re describing out of the box.
A process can be anywhere in the cluster, and you can interact with it as if it was on your local node.
I use all of these facilities in production on my product with ease. I’m happy to answer your specific questions.
(One of the original devs for The Outline here) so happy that it is able to live on, frozen in time, although missing a lot of the features that made it cool.
A lot of the cool things we were doing at the outline were on the CMS side of things, its a shame we were never able to share it
Lmao wow that’s a stretch
My understanding is that they cause a lot of page fragmentation, which leads to excessive writes to the WAL