Looking at this, it has similar aspects as ASP.NET Core, and the same flaws as the Controller per class design used. Methods such as "index", "show" and "store" do not share a state, they shouldn't share a class either.<p>However, you can rectify this, by just not trying to share a class with any of those. In .NET Steve Smith, aka Ardalis shows how to do this with his Clean architecture [1]. One idea is to make a class for each endpoint. This also makes it easier for "Update" classes to share functionality with other "Update" classes and so on.<p>[1]: <a href="https://github.com/ardalis/CleanArchitecture/tree/main/sample/src/NimblePros.SampleToDo.Web/Projects">https://github.com/ardalis/CleanArchitecture/tree/main/sampl...</a>
Nah, if you want heavy backend, go with Go/Ktor/C#, not node. If you want light backend, use sth like Hono or H3. If you want to primarily produce html, use Remix or Next.<p>Adonis/Redwood/Nest is something you will regret in few years because it will lock you down to "their" ways of doing things instead of something with replaceable components.<p>Admitted, Adonis looks most sensible out of these 3. Redwood is poisoned with needless GraphQL and Nest is written like 2008 java.
In Adonis you can at least pick the db layer.<p>But even Adonis locks you to their validator instead of Zod or his cousins, they use their own Request/Response classes instead of the platform ones, has yucky inheritance and annotations magic etc.
I used it for 3 years where everything which was too important (a took a long time to be done by the only maintainer (Harminder Virk) at that time with his only one "helper" (Romain Lanz) , so long that I had to stop using it because it was difficult to use in those conditions.
Hehey! I'm late for the party :D I just wanted people interested in frameworks to take a look on comparison with (my) framework which purposefully takes another approach <a href="https://news.ycombinator.com/item?id=40743058">https://news.ycombinator.com/item?id=40743058</a>
I never understood why you need more than a simple expressjs server. After all nodejs works best if served directly after a load balancer. But before heavy duty application logic. Node is fast in accepting, forwarding and replying requests. Put your real work in small c# or golang apps.
Has anyone tried both AdonisJS and RedwoodJS and can compare the two?<p>Adonis and Redwood are both trying to be the JavaScript version of Rails/Laravel - a traditional active-record based MVC rapid development server application framework.<p>The last time I looked for one of these (2018) they were immature and now at least in terms of website and documentation they both appear very capable. But if there’s one thing that JS libraries are good at, it’s marketing and slick documentation.<p>So, curious to hear any experiences with either and especially both.<p>Is it actually good?
No mention of Views? The one thing I'd love to understand and is missing vs. Rails/Laraval is an integrated solution of solving the View part of MVC I think?<p>Looks like a really beautiful framework.<p>EDIT: Nevermind, it's in the docs, just not on the main landing page so feels a little more secondary. TLDR they recommend you use Edge/Pug/Nunjucks, htmx, vite for css bundling. Nice!<p><a href="https://docs.adonisjs.com/guides/views-and-templates/introduction" rel="nofollow">https://docs.adonisjs.com/guides/views-and-templates/introdu...</a>
Anyone else see these types of announcement posts, and it's like they already have thousands of users? Where do y'all learn about these projects so early?