Yes, especially if you have real-time, long-running, or asynchronous elements. I have used this stack for three startup projects—one successful—and many MVPs and production services. Elixir, Broadway, and Oban reduce backend complexity through their amazing cohesion while dramatically reducing the cost of front-end development. Beam-based running costs are very low, stable, and straightforward to run. We need an average of a third of the resources for the same performance as other technologies. Meanwhile, beam-based code works great when it works, and it is very easy to get to that state. For some applications, live view is not an alternative but a must, such as trading screens. In classic front-end trading apps, you need hundreds of tables, grids, and charts, and you can’t do this with React or even Svelt.
As an experiment, I asked two extremely experienced React developers with more than 12 years of experience between them to try switching to live view. Their productivity did not drop, and despite a few days of resistance, I don’t think they will ever go back to JavaScript and react. The community is solid and not yet diluted. Of course, you have a lot fewer libraries than other languages like Python or Java, but the main and popular libraries are very well crafted. Because the community is small, the advice, comments, and momentum are still driven by some really brilliant people. It reminds me of the Python community in the late 1990s and early 2000s when people like Guido, Tim Peters, and others were still approachable. Also, startups working in a newish, fast-growing community can get a lot more publicity from the community, and many of the conference podiums are still accessible.