31–40 of 69 posts
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?
This is getting popular due to the recent 'Laravel vs JS Frameworks' controversy. https://www.youtube.com/watch?v=yaodD79Q4iE
Lack of vite/webpack/... FE integration is a huge breaker.
[flagged]
Has anyone tried both AdonisJS and RedwoodJS and can compare the two? 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. 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…
I haven't used either so I can't chime in on that front, but long ago I was pretty into Sails which is written by a team that loves rails, but switched to NodeJS so it's basically Node on Rails. I actually thought they discontinued it, but I just searched and it still exists. It was a solid framework like 5 years ago when I used it last so I assume it's quite mature now. https://sailsjs.com/
Personally though, I'm just done with server side JS and the dependency hell coming with it.
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? Looks like a really beautiful framework. 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! https://docs.adonisjs.com/guides/vie…
Maybe it's because it's (mostly) markup, but Pug is the only whitespace language that I really gel with. I wish it had more support across the board! Maybe it's the years of Emmet use that's got me biased. I remember getting excited about both of these before they each changed names.
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. 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…
As a convention I don't think one method per verb in a controller is inherently bad just because they don't share state. Plenty of long running, maintainable projects follow this practice.
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.
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. 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. Admitted, Adonis looks most sensible out of these 3. Redwood is poisoned w…
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.
Heck. 3yrs is quite long. Ill drop anything that doesn't allow me to ship daily