Live data from Hacker News

AdonisJS

adonisjs.com

51–60 of 69 posts

Re: AdonisJS

#51

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…

So don’t use their opinions, use mine.

Until the next dev comes to the project and doesn’t agree with your opinions, right? I’ve seen this movie far too many times.

The main benefits of these frameworks is that they remove all the bike shedding decisions. And I trust more something used by a lot of people and battle proven even if I don’t 100% agree with everything.

What you think is the best library for validations is just an opinion as theirs, and for example I don’t think Zod is good at all. See? Now on a team of 5 people we have 6 different preferences and we have to schedule 10 meetings to decide what library is best. And next month we will regret using it anyways.

There is a reason Rails, Laravel, Django etc are so popular in their ecosystem.

I honestly don’t believe the “I can do better all of this by myself”. It’s usually an undocumented, unproven, buggy and insecure mess that only the main author knows how it works.

Re: AdonisJS

#52

Earlier quoted context omitted.

Locking things in is not an issue if things are well built and well maintained. Having used Laravel, I'm amazed at their DX. First party libs all built by the same team, tools also built by the same team. Everything is congruent and just flows. Compare that to the wild west that is Javascript land. Multiple libraries that all do the same thing in different ways. Stuff being deprecated or completely changed. Sure, if…

"Locking things in" is an issue. It might not be a too big issue but it is one definitely. Consider choosing Oracle as your database. It is a great database maintained by a big company so it will be around in future too. But you will be locked-in to very expensive licensing because when big businesses are "locked in" Oracle can and will raise their prices.

Terrible example.

Re: AdonisJS

#53

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…

What are "heavy" vs "light?" Featureful middleware/plugin ecosystem vs stdlib+process forking?

And/or are we talking minimum memory footprint?

Re: AdonisJS

#56

Earlier quoted context omitted.

PHP world is different. There's only Laravel and Symfony. You can't count on both surviving till atomic winter. As you say, js world is fickle and I wouldn't count on Adonis being here for a long time. Mix and match is more pragmatic in this setting.

Lol, Symfony was released in 2005 and Laravel in 2011. PHP is much older. They've been around for long time and will stick around for many winters.

Oops I made a typo, I meant you CAN count on them surviving

In Js world it's better to not bet everything on a single horse

Re: AdonisJS

#57
post #7

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?

[deleted]

Re: AdonisJS

#58

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…

[deleted]

Re: AdonisJS

#59
post #4
post #2

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…

Grouping related functionality in a class and using it as a namespace, and using inheritance to get a few useful common features in close proximity and handing hooks is perhaps not the most correct from an OOP perspective, but it's common and results in much less boilerplate than doing everything 'correctly'. What's more egregious to me is that the methods should just match HTTP method names and have 1 controller per…

What about just having request handling functions in a single file or a directory?

Re: AdonisJS

#60
post #35

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…

An official mention of Pug? Now, they got me listening. 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.

I heavily dislike Pug, just because it depends on indentation. Maybe I'm just my IDE somehow wrong, but trying to rearrange things seems always so much more complicated and trying to learn this clever syntax instead of doing normal html.
Post reply on HN