4 ms·
Phoenix is obviously “the big thing” and no other language/framework combination has something as good as LiveView. Rails cannot compete there. Other than that
by cschmatzler 3y ago
Phoenix is obviously “the big thing” and no other language/framework combination has something as good as LiveView. Rails cannot compete there.
Other than that, building Livebook apps for our customer success team has been really great and easy.
There’s quite a big push for ML in Elixir right now, and then there’s also Nerves for embedded programming, which I’ve never dabbled in but it looks nice.
- OkayPhysicist 3y agoLiveView is definitely Elixir's killer app. It's what takes Phoenix from "a really good web framework" to "the singular best web framework", in my experience. Ecto is also a best-in-class data-layer adapter (ORM seems wrong and reductive).
- sethammons 3y agoI'm primarily a Go developer who loathes ORMs. I have to admit that Ecto is pretty great.
- cultofmetatron 3y agoecto is also just an amazing db wrapper in general. you basically write sql in elixir which means you can optimize the crap out of your queries and its easy to steop down to actual sql where needed via fragments.
- hosh 3y agoAnd you can still use composable queries if you still want to (equivalent to Rail’s named scopes).
- slekker 3y agoDo you have any write up about Livebooks for your CS team? Sounds like an interesting use case!
- metaltyphoon 3y ago> no other language/framework combination has something as good as LiveView You just have to look. Blazor does what LiveView do and on upcoming. NET 8 it will leapfrog it.
- porker 3y agoPeople have been saying this about Blazor for years, and it's never reached that point. Where can I see what .NET 8 will bring to Blazor to change this?
- OkayPhysicist 3y agoAs someone currently using bleeding edge Blazor at work, and Phoenix on my own time, this is wromg to the point of comedy. The big thing that LiveView has going for it is that it transforms the client session into just another process to communicate with, using the same message passing tools as the rest of the language, with very little headache because concurrency is already an expectation. Blazor can never achieve this, because C# is not a concurrency focused language.