Post

I don't think it's just contexts' fault. I think it's also too much boilerplate that's needed to achieve basic stuff and LiveView not being part of the framework + its design with views and components being two different things. It's still the best stack on the planet if you asked me 🙃 (1/2)

I feel that recent shift from views to components does similar thing. I still cannot fully comprehend how I should handle JSON-only routes with that approach or how I should handle routes that return different format depending on the `Accept` header or URL extension.

hexdocs.pm/phoenix_view... about that. I understand a little what they mean there, but the documentation of that is so poor that I believe that most of the newcomers will just say "f… that shit" and will go somewhere else. The recent drifts in Phoenix are quite putting off.

If anything I would prefer new projects to shift from `MyAppWeb.FooController` to IMHO "more natural" naming scheme of `MyAppWeb.Controllers.Foo` to match file path just like it is standard in other Elixir projects.

IMO it should be `MyAppWeb.Foo.Controller`. The plural naming goes against the informal lang convention (e.g. `List`, `Map`), and things are better grouped per scope (foo controller, view, layout, ...).