hibbitybibbity

5 ms·

1.
by hibbitybibbity 1y ago
Elixir/Erlang is best for building long-running systems that you don't want to go down. Erlang's creators optimized for stability (phone systems) and sort of reinvented concurrency and distribution in support of that goal. Th
2.
by hibbitybibbity 1y ago
I thought I would miss static typing more than I do. Elixir's pattern matching is actually extremely powerful in its own right.
3.
by hibbitybibbity 1y ago
Oh baller
4.
by hibbitybibbity 1y ago
Not really because Phoenix handles the web layer while Ash handles the domain/application layer. In other words Phoenix provides one interface, of potentially many, through which users could access an application built in Ash. Which is
5.
by hibbitybibbity 1y ago
You sound a lot like me when I first approached Ash a year ago, especially the part about being new to Elixir and worrying I'd just reproduce my prior MVC frustrations (Laravel in my case) in Phoenix. I've been using Ash for about
6.
by hibbitybibbity 1y ago
Just wanna chime in and say expr is the bomb
7.
by hibbitybibbity 1y ago
I came to Elixir from PHP/Laravel so I approached Ash with a similar skepticism. I was looking specifically for a set of tools that would allow me to rebuild an ancient and unwieldy ColdFusion SAAS product, as a solo dev, with maximum
8.
by hibbitybibbity 1y ago
When I was first getting started with Ash I also found the documentation to be frustrating at times. It's less of an issue for me now that I'm more familiar with it. I asked a lot of questions in the discord and found them to be s
9.
by hibbitybibbity 1y ago
I've got an app coming out of beta that runs web accessibility scans, which uses Elixir+Ash. Beta testers loved it, it's been very stable and I barely had to touch it over the beta period. This app has a lot of complex headless br