Elixir's Phoenix framework is not hard to learn at all if you've learnt Angular (post 2.0, so the one not to be confused with AngularJS) before.
Not even the storage is difference despite one being a front-end framework and the other a monolith. With angular you keep a singleton to communicate with storage and you toss it around component to component, with Phoenix you have another singleton: Repo.
I still think Phoenix could benefit from being a bit more decoupled from Ecto.
@maikel I really like the ideas behind https://github.com/woutdp/live_svelte which makes liveviews nicer IMO
Agree about Ecto though
@Unlogic Ecto is too ....hmm...how do I put it:
hmmm...
Anti-NoSQL
In a world where we have Redis, Mongo, CouchDB and a very long list of other NoSQL engines that allow for much quicker adaptation to the type of data, that continously writing migrations and relations
@Unlogic I'm not in favour of Svelte though I think most JS frameworks need to die.
Tailiwind and LiveView.JS can do it all. Most people doing LiveView IMHO don't seem to pay attention to the later.
@Unlogic I heard that before from ...let's see if I can remember the name: DaisyUI.
When all that can be achieved editing app.css
I mean if you use the same classes for buttons, titles, etc, all that doesn't need to be on your HTML at all. Those are base styles for Tailwind
Maikel 🇪🇺 🇪🇸
Unlogic