top | item 43995574

(no title)

butterNaN | 9 months ago

That is categorically not "how things are done" in the Elixir world. Have you considered that the Advanced Next Token Predictor may be imperfect?

discuss

order

__jonas|9 months ago

It kind of is though, regardless of what the LLM did there, the 'happy path' with something like Phoenix is using the phx.new and the generators which gives you a ton of files and structure that is a bit overwhelming for people used to more 'minimalist' web frameworks.

Check this out this guide from the Phoenix docs:

https://hexdocs.pm/phoenix/json_and_apis.html

That's a ton of stuff just to return some JSON from an endpoint. Sure the structure probably helps when you get into big complex projects, but for a beginner not used to this style of framework it looks like a lot.

pessimizer|9 months ago

Elixir is to Phoenix as Ruby is to Rails. The original comment was about Elixir, not Phoenix.

It also explicitly mentions Flask, which would be inane to directly compare to either Phoenix or Rails. How complex is your Django app, Mr. Python?

bn-usd-mistake|9 months ago

Isn't Phoenix more like Django (rather than Flask) which would also generate multiple files?