Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AdonisJS

adonisjs.com

Post reply on HN
Print view View original

61–69 of 69 posts

Re: AdonisJS

#61

Post by itslennysfault »

sureglymop wrote: post #34
itslennysfault wrote: post #5

Earlier quoted context omitted.

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/

I think something that is somewhat similar but even more fleshed out than Sails is NestJS. Personally though, I'm just done with server side JS and the dependency hell coming with it.

NestJS is my go to and the reason why I haven't touched Sails in years, but it is more "Angular for the backend" than "Rails for JavaScript" imo.

but I probably should've mentioned it anyway since it has been my node backend framework of choice for quite a while.

I'm kinda with you on that though. I'm actually currently prototyping new services in DotNet Core and am really enjoying it so far.

Re: AdonisJS

#62

Post by OptionOfT »

Ciantic wrote: 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…

The idea was that a controller is instantiated per request, so constructor and then your method, index / post / list / ...

You could use your constructor as a shared place to set up the requirements for your method.

Re: AdonisJS

#63

Post by charlie0 »

morbicer wrote: post #56
charlie0 wrote: post #47

Earlier quoted context omitted.

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

The fact that people (the builders) don't bet on a single horse IS the reason why we are in the state JS world is in. The only person that readily comes to mind is Evan You, who's been working on and driving Vue JS for a very long time. Of course, Vue JS is not a framework.

Adonis is starting to get there, but I don't know much about the core team and how long they've been working on it. If they are able to focus on delivering core features and not getting distracted by every wave that hits the JS world, eventually the level of convenience they provide will reach a tipping point and developers will flock to it.

Re: AdonisJS

#64

Post by morbicer »

charlie0 wrote: post #63
morbicer wrote: post #56

Earlier quoted context omitted.

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

The fact that people (the builders) don't bet on a single horse IS the reason why we are in the state JS world is in. The only person that readily comes to mind is Evan You, who's been working on and driving Vue JS for a very long time. Of course, Vue JS is not a framework. Adonis is starting to get there, but I don't know much about the core team and how long they've been working on it. If they are able to focus on…

I think there are multiple reasons why JS world is different.

- JS libs often target browser as well and that's a fast moving target

- JS is primary language of serverless which is also moving fast

- it attracts younger devs chasing hot trends

- the fragmentation is already there, people got used to it and some even embrace it

I lead development on a 12 year old SPA. It's a Ship of Theseus where there is almost zero original code but we never had to rewrite from scratch, instead we were swapping piece by piece as we went. The time investment was reasonably small and we never endangered the business with the full rewrite. I shudder at possibility that someone before me picked "batteries included" AngularJs (the V1). A sibling project is still fighting it today!

Re: AdonisJS

#66

Post by begueradj »

amanvirk wrote: post #42
begueradj wrote: post #40

Earlier quoted context omitted.

You must be its creator (Harminder Virk) because this is the type of responses (much worse ones, to be accurate) you were used to provide for anyone who asks you about something.

That was sarcasm on your original comment that you have edited 3 times. Anyways, don't take it seriously and have fun

If you check my Github profile, you will see I still have on my list of starred repositories several of yours. I also still have at least 2 articles on my blog related to AdonisJs. I hope you understand what I mean.

Re: AdonisJS

#67

Post by husarcik »

charlie0 wrote: post #18
jitl wrote: post #3

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 looked at AdonisJS, but it has soo many things missing that I'd rather just go with Laravel or Rails. Both of those have been around for so long and have an amazing ecosystem (especially Laravel) and are battle tested. I've also just lost my trust in JS for any serious long term projects. Things work at first and then a year later all the underlying dependencies have changed and stuff stops working.

What is missing for you? I don't see much missing anymore coming from Laravel. There are a few things which I wish were more batteries included, such as "forgot password" but that can be made in minutes with code so it's not a big issue.

Re: AdonisJS

#68

Post by antifa »

holoduke wrote: post #30

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.

What I look for in an expressjs alternative is 1.) First class typescript support 2.) Better tree shaking.

Re: AdonisJS

#69

Post by antifa »

jatkindev wrote: post #50
holoduke wrote: post #30

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.

Curious, why do you say Node.js works best served directly after a load balancer? Genuinely just wondering, never heard this before.

Almost all high level backends (node, php, python, ruby, etc.) work best behind a load balancer.
Post reply on HN