"Still" implies that one would have chosen it before. Ironically, one of the reasons my startup died was using Elixir as if it was Rails[1]. Even aside from t

"Still" implies that one would have chosen it before. Ironically, one of the reasons my startup died was using Elixir as if it was Rails[1]. Even aside from type safety considerations: in RoR variable bindings appear out of thin air! Imagine onboarding a new developer – not only do they need to learn the arcane language, but then they need to learn a bunch of non-hygienic macros! I remember the lightbulb moment when I was patching Ruby's Devise authentication library to add verifiable credentials to it when I realised that a variable used there is not a 0-ary function, but actually something that is just bound in context by magic. Also, even Rails experts have to go on a hunt to understand magic[2] too! I would personally just use typescript bridged to rust to preserve types ans sqlx for type-safe queries to the database. Or use something like bubble.io if you want to iterate on ad hoc things until you get there! [1]: https://memorici.de/posts/pre-mortem/ https://memorici.de/posts/pre-mortem/ [2]: https://medium.com/launch-school/params-in-rails-where-do-they-come-from-b172cdb46eb4 https://medium.com/launch-school/params-in-rails-where-do-th...