4 ms·
Am I the only one who is not impressed by the LiveView? 2 things that bother me: 1) It seems most of these walk-throughs omit the process of actually designin
by ewuhic 5y ago
Am I the only one who is not impressed by the LiveView?
2 things that bother me:
1) It seems most of these walk-throughs omit the process of actually designing the application architecture ("structure") so copy-pasting what had already been well-thought over feels organic;
2) Once you're faced with a more complex (production mission critical) task, the automagic starts to fade and you're back to the good ol' business logic and ui programming.
- mrkurt 5y agoI just built my first LiveView app in anger last month. I don't really what you mean, though. If it helps, I built my app the same way I would have built a Rails app: 1. Create a migration and some files to map DB tables back to my app 2. Create views and wire them up to the database The automagic was 80% of the automagic in Rails. LiveView isn't giving me automagic, exactly, it gives me a way to interact with the browser. One reason I may not understand what you're saying is: I didn't design my application architecture. I started with a small part and just built the rest incrementally.
- nesarkvechnep 5y agoUsing LiveView doesn't in any way equal to writing spaghetti mixing presentation with logic.
- prophesi 5y agoThe reason they "omit" the process of designing the app architecture is that running `mix phx.new` does that for you. Or `mix phx.gen.live` for an existing Phoenix project. Coding a LiveView Phoenix project is identical to coding a non-LiveView Phoenix project, except the module that handles rendering your pages now has additional functionality out-of-the-box.